pact CLAUDE.md

pact CLAUDE.md is an instructions file for coding agents from jmcentire/pact. It costs 6,590 tokens per session, scanned A, original, MIT.

Instructions and command reference for Pact, a software tool that breaks projects into contracts and tests before separate components are implemented.

In plain words
What is it for?
Use them to operate Pact from the command line, apply build specifications, generate tasks, or inspect component and production-readiness information.
Why use it?
They provide the workflow for initializing projects, building components, analysing requirements, and checking project status.

Instructions file

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.

agentmods
npx agentmods add instructions/jmcentire/pact/claude-md
Clone the repo
git clone --depth 1 https://github.com/jmcentire/pact

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for pact CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jmcentire/pact/claude-md.svg)](https://agentmods.dev/instructions/jmcentire/pact/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/jmcentire/pact/claude-md"><img src="https://agentmods.dev/badge/instructions/jmcentire/pact/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 6,590 This file is loaded in full into every session.
When invoked 6,590 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.06590 $0.06590
Opus 5 $0.03295 $0.03295
Sonnet 5 $0.01318 $0.01318
Haiku 4.5 $0.00659 $0.00659

Measured 4d ago against content hash 144fb865cb26, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pact CLAUDE.md 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 4d ago.

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.md · 518 lines

How it starts

The opening of the file, as written. The whole thing — 518 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md -- Pact

Contract-first multi-agent software engineering. Decomposition produces contracts and tests, not code. Black-box implementations verified by functional tests at boundaries. Recursive composition.

Quick Reference

cd ~/Code/pact
python3 -m pytest tests/ -v        # Run all tests
pact init <project-dir>            # Initialize project
pact init <project-dir> --spec <file> # Initialize from AI-authored JSON/YAML build spec
pact spec apply <project-dir> <file> # Apply AI-authored JSON/YAML build spec
pact status <project-dir>          # Show state
pact components <project-dir>      # List components
pact build <project-dir> <id>      # Build specific component
pact run <project-dir>             # Execute pipeline
pact tasks <project-dir>           # Generate/display task list
pact analyze <project-dir>         # Cross-artifact analysis
pact checklist <project-dir>       # Requirements quality checklist
pact production init <project-dir> # Scaffold optional production-readiness pack
pact production fingerprint <project-dir> # Print the source fingerprint for evidence
pact production validate <project-dir> # Validate production-readiness gate for a Pact-managed project
pact assess <directory>            # Architectural assessment (any codebase)
pact export-tasks <project-dir>    # Export TASKS.md
pact handoff <project-dir> <id>    # Render/validate handoff brief
pact review <target> --claim <text> # Advocate + Simulacrum review
pact agent spec-author [--apply]    # Run one constrained spec-author agent
pact agent repair --source-root <dir> [--apply] # Run one constrained repair agent
pact directive <project-dir> <json> # Send structured directive to daemon
pact mcp-server [--project-dir <dir>] # Run MCP server (stdio)
pact-mcp                              # MCP server entry point

Entry point: pact = "pact.cli:main", pact-mcp = "pact.mcp_server:main" (pyproject.toml)

Python: >=3.12 | Dependencies: pydantic>=2.0, pyyaml>=6.0 | Optional: anthropic>=0.40, mcp>=1.0

Read the full file on GitHub · 518 lines

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. 4d ago First seen · 518 lines · 6,590 tokens per session scan A 144fb865cb26

Subscribe to this mod's changes

pact CLAUDE.md is an instructions file published in the GitHub repository jmcentire/pact (164 stars, last pushed 14d ago), licensed MIT. It adds 6,590 tokens to every session, about $0.0330 per session on Opus 5. 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens