Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/varienos/agentic-workflownpx agentmods add commands/varienos/agentic-workflow/bug-hunter.skeletonWrote 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-hunter.skeleton)<a href="https://agentmods.dev/commands/varienos/agentic-workflow/bug-hunter.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/bug-hunter.skeleton/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/varienos/agentic-workflow/bug-hunter.skeleton"><img src="https://agentmods.dev/badge/commands/varienos/agentic-workflow/bug-hunter.skeleton.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02238 |
| Opus 5.5 | $0.00000 | $0.00895 |
| Sonnet 5.5 | $0.00000 | $0.00448 |
| Haiku 4.5 | $0.00000 | $0.00224 |
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 1mo 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Hunter — Autonomous Error Detector and Corrector
Extracts the issue description, identifies the cause, corrects it, tests it, and commits. Usage:
/bug-hunter <issue_description>,/bug-hunter "item cannot be added to cart"
Step 1 — Extracting the Issue Description
Extract the following information from the user's bug report:
| Field | Description | Example |
|---|---|---|
| Description | What's happening? | "Item cannot be added to cart" |
| Expected behavior | What should happen? | "Item should be added to cart" |
| Context | Where is it happening? | "Web application, item detail page" |
| Repeatability | Is this happening every time? | "Every time" / "Sometimes" |
| Error message | Is there an error message? | "TypeError: Cannot read property..." |
RULE: If the report is vague, do not ask a question. Analyze with the information you have.
Step 2 — Investigation of Similar Errors
Have similar errors already been fixed? In the case of episodic memory:
- Similar error descriptions
- Same module/directory previous fixes
- Repeated error patterns
If found:
- Reference to previous solution
- Why is this similar? Investigate further
- Is regression or a different error distinguished?
Step 3 — Cause Analysis
3.1 — Narrow Down Scope
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.
- 1mo ago Changed · -24 lines 0075a170bf7a
- 1mo 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 (59 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,238 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
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
github
(dev-only) github maintainer harness — GitHub issue-fix and PR-review via gh CLI. NOT distributed to user projects.
revdiff
Review git diff with revdiff TUI, then act on its annotations.
al-pr-prepare
Prepare a clean, documented pull request draft for AL features or fixes with summary, testing notes, and checklist. ALDC workflow (Copilot prompt al-pr-prepare); invoke explicitly.
pr-manager
Comprehensive pull request management with ruv-swarm coordination for automated reviews, testing, and merge workflows.
bug
Report a bug from a plain description — triggers investigation, structured documentation and fix coordination.