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.
npx agentmods add skills/jmcentire/pact/pact-engineernpx skills add jmcentire/pact --skill pact-engineergit clone --depth 1 https://github.com/jmcentire/pactWrote 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.
[](https://agentmods.dev/skills/jmcentire/pact/pact-engineer)<a href="https://agentmods.dev/skills/jmcentire/pact/pact-engineer"><img src="https://agentmods.dev/badge/skills/jmcentire/pact/pact-engineer.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00088 | $0.01209 |
| Opus 5 | $0.00044 | $0.00605 |
| Sonnet 5 | $0.00018 | $0.00242 |
| Haiku 4.5 | $0.00009 | $0.00121 |
Grade A, and why
pact-engineer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pact Engineer
Use Pact to make the implementation bet explicit before coding. Keep Pact's contracts and tests authoritative, but treat planning and implementation as a feedback loop rather than a one-way handoff.
Workflow
- Source
~/.profilewhen feasible. - Start or resume a Kindex session, then search the task and affected domain.
- Read repository instructions and the relevant implementation, tests, and recent history before framing the change.
- Normalize vague task language into a concrete problem statement,
boundaries, constraints, and acceptance criteria. Use Constrain artifacts
when available; otherwise create equivalent
prompt.mdandconstraints.yamlinputs. - Run central architecture claims past Simulacrum before locking the frame.
- Run Pact in plan-only mode and advance it through interview/decomposition until it pauses after contracts and tests:
pact init "$PACT_DIR" --budget 10
pact run "$PACT_DIR" --constrain-dir "$CONSTRAIN_DIR" --plan-only --once
Answer or approve interview questions as needed, then continue pact run --once until the plan-only pause. Do not bypass unresolved ambiguity.
- Read
design.md,.pact/decomposition/tree.json, contracts, visible tests, and generated task lists. Runpact assesson the affected source tree. - Render a focused brief before implementing each component:
pact handoff "$PACT_DIR" "$COMPONENT_ID" --validate --max-tokens 2000
- Implement directly with the active agent. Follow the repository's existing patterns and verify incrementally.
- Reconcile contracts whenever implementation exposes infeasibility:
- Stop instead of silently deviating.
- Record the conflict and the failed assumption in Kindex.
- Update task/constraints/contracts and regenerate affected tests or rerun Pact plan-only.
- Resume only after the contract and implementation agree.
- Run repository tests, type checks, lint,
pact validate, andpact auditwhere applicable. Then run the lean review checklist in references/lean-review.md: remove ceremony that does not improve correctness, recovery, observability, or evidence, but do not delete safety or production-readiness controls. - Run post-implementation review:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 111 lines · 88 tokens per session scan A b5cae1ea1722
pact-engineer is a skill published in the GitHub repository jmcentire/pact (164 stars, last pushed 15d ago), licensed MIT. It adds 88 tokens to every session and 1,209 once invoked, about $0.0004 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…