Agent Plugins Marketplace
← All plugins

chip-contract

v0.4.0

Teaches your agent the chip lifecycle and the socket beneath it: whether a behavior should be a chip at all, seating a function's code-or-model decision in a socket, authoring the package, the fixture suite that gates authority, installing so it resolves, auditing silent failures, and closing the outcome loop.

CodexClaude Code8 Skills

By Marc LavalleeLicense: MIT0 GitHub starsUpdated last week

Directory evidence

Runtimes
Codex and Claude Code
Parsed components
8 skill or MCP entries
Source updated
Oct 12, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install chip-contract for Codex and Claude Code

Installs for the current user
codex plugin marketplace add IchenDEV/agent-plugin-mkt
codex plugin marketplace upgrade agent-plugin-marketplace
codex plugin add chip-contract@agent-plugin-marketplace

Paste and run these commands in a terminal with Codex. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/lavallee/chip

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The repository root is the plugin root.

Plugin files

chip-contract/
├── .codex-plugin/plugin.json
├── .claude-plugin/plugin.json
├── skills/chip-audit/SKILL.md
├── skills/chip-author/SKILL.md
├── skills/chip-candidate/SKILL.md
├── skills/chip-evaluate/SKILL.md
├── skills/chip-fixtures/SKILL.md
├── skills/chip-install/SKILL.md
├── skills/chip-outcome/SKILL.md
└── skills/chip-socket/SKILL.md

Included Skills8

chip-auditskills/chip-audit/SKILL.md

Read a chip's receipts to find dark installations, fallback streaks, capped authority, and digest mismatches — invoke on a cadence, after any host deploy, and whenever a chip "seems fine" but nothing it recommends ever happens.

chip-authorskills/chip-author/SKILL.md

Author a chip package from one operational promise — invoke after chip-candidate says "chip", or when adapting an existing package to a new contract version.

chip-candidateskills/chip-candidate/SKILL.md

Decide whether a behavior should become a chip, stay a skill, or remain a plain prompt — invoke before authoring anything, and whenever someone says "we should make this a chip".

chip-evaluateskills/chip-evaluate/SKILL.md

Run a chip's held-out suite, record the evaluated tuple, and explain why authority is capped — invoke before lifting a binding above observe, after any model or profile change, and whenever a chip proposes effects that never dispatch.

chip-fixturesskills/chip-fixtures/SKILL.md

Build the fixture suite that gates a chip's authority — invoke while authoring, before any evaluation, and whenever a production failure has no fixture that would have caught it.

chip-installskills/chip-install/SKILL.md

Bind and install a chip package against a host, with the preflight that catches unresolvable packages — invoke when wiring a circuit into a host, and before every deploy of a host that runs chips.

chip-outcomeskills/chip-outcome/SKILL.md

Wire a host to emit outcome receipts so a chip can be calibrated rather than merely evaluated — invoke when a host consumes a chip's judgment to make a decision, and whenever someone asks whether a chip is actually any good.

chip-socketskills/chip-socket/SKILL.md

Seat an existing function's code-or-model decision in a socket so every call is receipted and the escalation band can be learned — invoke when adding a model call to a function, when a heuristic-then-LLM threshold was guessed, or before deciding whether a behavior should move a rung on the ladder.

Plugin manifests2

.codex-plugin/plugin.json
{
  "name": "chip-contract",
  "version": "0.4.0",
  "description": "Teaches your agent the chip lifecycle and the socket beneath it: whether a behavior should be a chip at all, seating a function's code-or-model decision in a socket, authoring the package, the fixture suite that gates authority, installing so it resolves, auditing silent failures, and closing the outcome loop.",
  "author": {
    "name": "Marc Lavallee",
    "url": "https://github.com/lavallee"
  },
  "homepage": "https://lavallee.github.io/chip/",
  "repository": "https://github.com/lavallee/chip",
  "license": "MIT",
  "keywords": [
    "chips",
    "circuits",
    "sockets",
    "receipts",
    "authority",
    "operational",
    "contract",
    "portability",
    "distillation"
  ],
  "skills": "./skills/",
  "interface": {
    "displayName": "chip",
    "shortDescription": "Move the code-vs-model boundary on evidence.",
    "longDescription": "Eight skills over the chip contract: decide whether a behavior is a chip, seat an existing function in a socket so every call is receipted and the escalation band is learned from labels, author and fixture a package, install it so it resolves, audit for silent failures, and close the outcome loop.",
    "developerName": "Marc Lavallee",
    "category": "Developer Tools",
    "capabilities": [
      "Interactive"
    ],
    "websiteURL": "https://lavallee.github.io/chip/",
    "defaultPrompt": [
      "This function calls a model behind a heuristic. Should it be a socket, and what is the smallest change?",
      "Is this behavior a chip, a tool, a dialogic skill, or doctrine?",
      "Read these socket receipts and tell me where the code-vs-model boundary should move."
    ]
  }
}
.claude-plugin/plugin.json
{
  "name": "chip-contract",
  "displayName": "chip — portable operational components",
  "version": "0.4.0",
  "description": "Teaches your agent the chip lifecycle: deciding whether a behavior should be a chip at all, authoring the package, building the fixture suite that gates its authority, installing it so it actually resolves, auditing for the silent failures, and closing the outcome loop so the chip can be calibrated rather than merely evaluated. Eight skills over the contract in spec 0.6, including chip-socket: seating an existing function's code-or-model decision in a socket so the escalation band is learned from receipts.",
  "author": {
    "name": "Marc Lavallee"
  },
  "repository": "https://github.com/lavallee/chip",
  "license": "MIT",
  "keywords": [
    "chips",
    "circuits",
    "sockets",
    "receipts",
    "authority",
    "operational",
    "contract",
    "portability",
    "distillation"
  ]
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[chip-contract on Agent Plugins Marketplace](https://pluginsmp.com/plugins/chip-contract)