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/bug-triagegit 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/bug-triage)<a href="https://agentmods.dev/commands/iampawan/manifest/bug-triage"><img src="https://agentmods.dev/badge/commands/iampawan/manifest/bug-triage.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.1 | $0.00065 | $0.00489 |
| Opus 5 | $0.00032 | $0.00244 |
| Sonnet 5 | $0.00013 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
bug-triage 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 6d 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
/bug-triage
Invokes the bug-triage skill against the given contract.
Usage
/bug-triage <ID> # scope to one contract
/bug-triage # all contracts currently in their 4-week landing window
When to use it manually
The bug-triage skill normally runs every day automatically via the
launch-monitor.yml cron. You'd run it manually when:
- A known incident just happened and you want fresh data before the next cron tick.
- You're preparing for a stakeholder update and want today's bug list, not yesterday's.
- You're piloting Manifest without CI workflows installed yet and the cron isn't firing — manual is your only option.
- You're testing changes to the bug-triage skill itself.
What it does
- Reads
.manifest/contracts/*.mdto find contracts currently in their 4-week monitoring window. - For each: queries Sentry for new issues in the last 24h filtered to that release.
- Pulls qualitative signals from JIRA / support tools / app store reviews (if those MCPs are connected).
- Clusters findings by likely root cause.
- Dedupes against existing JIRA tickets (via Atlassian MCP).
- Files new tickets with contract back-references, severity, and reproduction steps inferred from stack traces.
- Appends to
.manifest/contracts/<ID>.bug-log.md. - Posts a daily summary to the contract's Slack thread.
Output
A markdown bug-log entry per affected contract, plus JIRA tickets filed, plus a Slack summary.
Anti-patterns
- Don't run this repeatedly in quick succession (the dedup logic handles overlap but you'll just be re-confirming the same data).
- Don't use this as a real-time error monitor — it's a daily-rhythm tool. Sentry alerting is the real-time path.
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.
- 6d ago First seen · 56 lines · 65 tokens per session scan A 7ff2869cf737
bug-triage is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 489 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
step-research
Always research before proposing a fix. The Untether bug you're chasing is often a known upstream engine quirk, a previously-fixed regression, or a documented config gotcha.
iterate-feature
Iterate on the feature "$ARGUMENTS" to fix issues and address feedback.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor.es
Diagnostica problemas de inferencia LLM en Mac: asiai doctor verifica el estado de los motores, conflictos de puertos, carga de modelos y estado de la GPU.