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-hunter.skeletongit clone --depth 1 https://github.com/varienos/agentic-workflowWhat 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.03059 |
| Opus 5 | $0.00000 | $0.01529 |
| Sonnet 5 | $0.00000 | $0.00612 |
| Haiku 4.5 | $0.00000 | $0.00306 |
Grade A, and why
bug-hunter.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 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Hunter — Otonom Hata Bulucu ve Duzeltucu
Hata aciklamasini alir, kok nedeni bulur, duzeltir, test eder, commit atar. Kullanim:
/bug-hunter <hata_aciklamasi>,/bug-hunter "sepete urun eklenemiyor"
Step 1 — Hata Aciklamasini Cozumle
Kullanicinin hata aciklamasından asagidaki bilgileri cikar:
| Alan | Aciklama | Ornek |
|---|---|---|
| Belirti | Ne oluyor? | "Sepete urun eklenemiyor" |
| Beklenen davranis | Ne olmali? | "Urun sepete eklenmeli" |
| Baglam | Nerede oluyor? | "Web uygulama, urun detay sayfasi" |
| Tekrarlanabilirlik | Her seferinde mi? | "Her seferinde" / "Bazen" |
| Hata mesaji | Varsa | "TypeError: Cannot read property..." |
KURAL: Hata aciklamasi cok belirsizse (orn. "calismıyor") bile SORU SORMA. Eldeki bilgiyle analiz et.
Step 2 — Hafiza Arastirmasi
Benzer hatalar daha once duzeltildi mi? Episodic memory'de ara:
- Benzer belirti iceren gecmis oturumlar
- Ayni modul/dosyada yapilan onceki duzeltmeler
- Tekrarlayan hata pattern'leri
Bulgu varsa:
- Onceki cozumu referans al
- Ayni kok neden mi kontrol et
- Regresyon mu yoksa farkli hata mi ayirt et
Step 3 — Kok Neden Analizi
3.1 — Kapsami Daralt
Hata aciklamasindan yola cikarak:
- Hangi alt proje? (API, Web, Mobile, Shared)
- Hangi modul/ozellik? (auth, orders, payments, ...)
- Hangi katman? (UI, service, data, config)
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 · 322 lines · 0 tokens per session scan A c052f1f1b235
bug-hunter.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,059 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
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
memory
Search, store, and manage AI Team Memory — agent expertise, decisions, learnings, and code patterns. File-based by default, with an optional memory MCP overlay.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
do-it-retrospective
开关本项目的本地行为反馈记录，或输出已记录问题的去敏复盘报告。参数为 on / off / status / report。.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
verify
Verify factual claims in content using deep research methodology - fact-checks key assertions and updates NCI scores.