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/varienos/agentic-workflow/bug-review.skeletongit clone --depth 1 https://github.com/varienos/agentic-workflowWrote 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/varienos/agentic-workflow/bug-review.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/bug-review.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/bug-review.skeleton.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.00000 | $0.03208 |
| Opus 5 | $0.00000 | $0.01604 |
| Sonnet 5 | $0.00000 | $0.00642 |
| Haiku 4.5 | $0.00000 | $0.00321 |
Grade A, and why
bug-review.skeleton 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 3d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Review — Hata Duzeltme Kalite Kontrolu
Bug fix commit'ini 3 perspektifle inceler: kod kalitesi, sessiz hatalar, regresyon riski. Kullanim:
/bug-review,/bug-review <commit_hash>,/bug-review HEAD~2..HEAD
Step 1 — Diff Cikar
1.1 — Arguman Cozumleme
| Girdi | Davranis |
|---|---|
| Bos | Son commit: cd ../Codebase && git diff HEAD~1..HEAD |
| Commit hash | Belirtilen commit: cd ../Codebase && git show <hash> |
| Range | Aralik: cd ../Codebase && git diff <range> |
1.2 — Diff Analizi
Diff'ten cikar:
- Degisen dosya listesi
- Her dosyadaki eklenen/silinen satirlar
- Degisikliklerin turu (duzeltme, test, config)
- Bug fix'e ozel: hangi satirlar "fix" icin eklendi, hangileri "test" icin?
KURAL: Diff bossa "Incelenecek degisiklik yok" deyip DUR.
Step 2 — 3 Ajan Spawn Et
Asagidaki 3 ajanin HER BIRINI paralel olarak calistir.
Ajan 1 — Kod Inceleyici (Bug Fix Perspektifi)
Gorev: Bug fix'in kalitesini ve dogru uygulanip uygulanmadigini kontrol et.
Bug Fix Kontrol Listesi (Sabit Cekirdek):
- Kok neden duzeltilmis mi? Belirtiyi mi yoksa kok nedeni mi duzeltmis?
- Minimal degisiklik mi? Sadece hata duzeltilmis mi yoksa gereksiz refactor da yapilmis mi?
- Ayni hata baska yerlerde de var mi? Benzer pattern baska dosyalarda da geciyorsa onlar da duzeltilmis mi?
- Regresyon testi yazilmis mi? Hatanin tekrarlanmadigini dogrulayan test var mi?
- Yan etkisi var mi? Duzeltme baska islevsellik bozuyor mu?
- Hata yonetimi uygun mu? Try-catch, error boundary, null check yeterli mi?
- Edge case dusunulmus mu? Sinir degerleri, null, bos dizi, concurrent erisim
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.
- 3d ago First seen · 262 lines · 0 tokens per session scan A 50dab130eb70
bug-review.skeleton is a command published in the GitHub repository varienos/agentic-workflow (58 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,208 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
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
toh-help
Display all Toh Framework commands and quick usage guide.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
feature
Create a feature specification using spec-driven development.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…