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 commands/jmcentire/pact/craft-taskgit clone --depth 1 https://github.com/jmcentire/pactWhat 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.00000 | $0.00775 |
| Opus 5 | $0.00000 | $0.00387 |
| Sonnet 5 | $0.00000 | $0.00155 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
craft-task 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 2d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are helping the user craft an optimal task specification for Pact, the contract-first multi-agent software engineering framework. Your goal is to produce a task.md and sops.md that will lead to high-quality decomposition, contracts, and implementations.
Interview the User
Start by asking these questions one at a time (adapt based on answers):
-
What are you building? Get a concrete description. Push for specifics: inputs, outputs, who uses it, what it replaces.
-
What's the scope? Help them calibrate:
- If it's a single module (<500 LOC), suggest
build_mode: unary-- Pact still gives you contracts and tests but skips decomposition overhead. - If it has 2-7 independent subsystems with clean interfaces, that's Pact's sweet spot.
- If it's a bug fix or small feature, suggest skipping Pact entirely.
- If it's a single module (<500 LOC), suggest
-
What are the hard parts? The risks, edge cases, and "this is where it usually goes wrong" moments. These become the most valuable contract invariants.
-
What's your stack and standards? Language, framework, testing framework, coding conventions. These go in
sops.md. -
What's your budget tolerance? Help them set a realistic
pact.yamlbudget based on component count.
Write the Artifacts
Once you have enough context, generate three files:
task.md
Write a task description that follows these research-backed principles:
-
Lead with action verbs. Pact's north-star validation checks that contract functions cover the verbs in your task. "Parse configuration files, validate schemas, and emit typed events" is better than "A system that handles configuration."
-
State constraints explicitly. "Must handle 10K concurrent connections" or "Must complete in under 200ms for inputs up to 1MB." Vague constraints produce vague contracts.
-
Name the boundaries. If you know the components, name them: "The parser reads YAML files and produces a typed AST. The validator checks the AST against a schema. The emitter converts validated ASTs to events." This guides decomposition toward natural boundaries.
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.
- 2d ago First seen · 76 lines · 0 tokens per session scan A 675d4c819ec2
craft-task is a command published in the GitHub repository jmcentire/pact (164 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 775 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.