pact

A plugin bundle for setting rules and checks around AI coding agents. It includes hooks, reusable procedures, project maps, and templates for coordinating agent work.

In plain words
What is it for?
Use it to enforce coding constraints, document system structure, guide development workflows, coordinate multiple sessions, and support visual prototyping.
Why use it?
It helps teams keep agent-made changes aligned with project rules and architecture instead of relying only on written instructions.

Plugin for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Claude Code
/plugin marketplace add jonathanmr22/pact
agentmods
npx agentmods add plugins/jonathanmr22/pact/marketplace
Clone the repo
git clone --depth 1 https://github.com/jonathanmr22/pact

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

pact scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude-plugin/marketplace.json · 26 lines

What it actually says

{
  "name": "pact",
  "owner": {
    "name": "jonathanmr22"
  },
  "metadata": {
    "description": "Programmatic Agent Constraint Toolkit — governance infrastructure for AI coding agents",
    "version": "0.9.1"
  },
  "plugins": [
    {
      "name": "pact",
      "source": "./plugins/pact",
      "description": "Hooks, skills, and templates for governing AI coding agents through infrastructure instead of instructions. Includes mechanical enforcement hooks, cognitive redirection skills, architecture map templates, lifecycle flow scaffolding, multi-session coordination, and visual prototyping workspace.",
      "version": "0.9.1",
      "author": {
        "name": "jonathanmr22"
      },
      "homepage": "https://github.com/jonathanmr22/pact",
      "license": "MIT",
      "keywords": ["governance", "hooks", "agent", "constraints", "infrastructure", "quality"],
      "category": "productivity"
    }
  ]
}
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 26 lines scan A b3ce8e0f0f24

Subscribe to this mod's changes

pact is a plugin published in the GitHub repository jonathanmr22/pact (15 stars, last pushed 2mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.