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/jonathanmr22/pact/pact-flownpx skills add jonathanmr22/pact --skill pact-flowgit clone --depth 1 https://github.com/jonathanmr22/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/jonathanmr22/pact/pact-flow)<a href="https://agentmods.dev/skills/jonathanmr22/pact/pact-flow"><img src="https://agentmods.dev/badge/skills/jonathanmr22/pact/pact-flow.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.00008 | $0.00307 |
| Opus 5 | $0.00004 | $0.00153 |
| Sonnet 5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
pact-flow 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.
What it actually says
Create a PACT lifecycle flow document for the feature the user specifies. Save it to feature_flows/{feature_name}_flow.yaml.
Read the relevant source code first to understand the feature's actual behavior. Then generate a YAML flow document covering:
- purpose — one sentence: what this feature does and why
- system_map_section — pointer to SYSTEM_MAP.yaml (don't duplicate structure)
- invariants — things that must ALWAYS be true
- states:
fresh_install— what exists, what's empty, what's defaultednormal_open— numbered order of operations + assumptionsbackground— what's active, held in memory, lostforce_close_reopen— what's lost, what's persisted, recovery pathbackground_resume— what re-initializes, what gets checkederror_paths— what happens when things go wrong
- gotchas — non-obvious interactions, race conditions, things previous sessions got wrong
After generating, present a verbal summary of the flow to the user for verification before finalizing.
Do NOT duplicate table names, file paths, or provider names from SYSTEM_MAP.yaml — use system_map_section to point there instead. This file owns BEHAVIOR (temporal). The map owns STRUCTURE (spatial).
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.
- 4d ago First seen · 25 lines · 8 tokens per session scan A 7825661fec83
pact-flow is a skill published in the GitHub repository jonathanmr22/pact (15 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 307 once invoked, about $0.0000 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
orloj-generator
Interactive scaffold generator for Orloj multi-agent systems. Use this skill whenever someone wants to create, set up, scaffold, bootstrap, or generate an Orloj agent system, pipeline, swarm, or hierarchy. Also trigger when users mention "orlojctl init", ask how to get started with Orloj, want to build a multi-agent…
nio-scan
Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.
memory-sync
Review the auto-extracted candidates in .claude/memory/pending.md and commit keepers to the canonical memory files (landmarks.md, libraries.md, decisions.md, landmines.md, conventions.md, pending-questions.md, backlog.md). Invoke at session start when the SessionStart hook reports pending candidates, or any time…
chore
Workflow track for tasks that need no TDD — documentation edits, governance count bumps, vendored-skill content updates, configuration tweaks, formatting, typo fixes, dependency bumps where no project code changes. Skips /scenario and /implement (no failing test to drive) and runs the work directly. archive…
spec
Draft a Workflow Phase 4 technical spec from an intake (and optionally a BRD + scout + research memo). The spec defines how the system will change: design (C4 + UML + dependency graph in PlantUML), data, APIs, tests, rollout, rollback. Output lives at docs/specs/ .md. Never self-approves — approval happens via…
design-ui
Orchestrates impeccable for every design task inside a workflow phase. Captures intent in natural language, classifies it (design / development / copy), translates design intents into a sequence of impeccable subcommand invocations, runs them in main context with state persistence at .claude/state/design/ .json, and…