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/iampawan/manifest/fixgit clone --depth 1 https://github.com/iampawan/ManifestWrote 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/commands/iampawan/manifest/fix)<a href="https://agentmods.dev/commands/iampawan/manifest/fix"><img src="https://agentmods.dev/badge/commands/iampawan/manifest/fix.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.00052 | $0.00459 |
| Opus 5 | $0.00026 | $0.00230 |
| Sonnet 5 | $0.00010 | $0.00092 |
| Haiku 4.5 | $0.00005 | $0.00046 |
Grade A, and why
fix 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
/fix
The fast path. For changes too small to deserve a contract.
Usage
/fix "OTP timer doesn't reset when app is backgrounded"
/fix https://your-org.atlassian.net/browse/PROD-1234
/fix "bump lodash to 4.17.21"
/fix "checkout button copy: 'Buy' → 'Buy now'"
Invokes the quick-fix skill: triage → fix → regression test → PR. No critics, no SLA, no launch report.
When to use /fix vs /contract
Use /fix (express) |
Use /contract (full) |
|---|---|
| One-line bug fix with clear repro | New user-facing behavior |
| Copy / CSS / config tweak | Needs a new analytics event |
| Dependency bump | Touches 2+ platforms |
| Localized to one root cause | Schema change |
| No new event / schema / platform | Edge cases genuinely matter |
| Minutes | Touches auth / billing |
/fix triages first. If your "quick fix" is actually a feature (adds
an event, spans platforms, changes the schema), it stops and points
you at /contract new — so the fast path stays safe.
When even /fix is overkill
For a literal typo, a single CSS value, or a config flip, just edit
the file and commit — no command needed. /fix is for small changes
you still want as a tracked PR with a regression test. If you don't
need either, skip it.
Output
- A lightweight fix record at
.manifest/fixes/<ID>.md - The fix + a regression test (in the repo's stack)
- A PR titled
[FIX-NN] <title>
No contract, no behaviors, no critics. Proportional to the change.
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 · 51 lines · 52 tokens per session scan A ad529ef55cb2
fix is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 2d ago), licensed MIT. It adds 52 tokens to every session and 459 once invoked, about $0.0003 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-31.
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.