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/parslee-ai/neo/bug-autonomousgit clone --depth 1 https://github.com/Parslee-ai/neoWrote 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/parslee-ai/neo/bug-autonomous)<a href="https://agentmods.dev/commands/parslee-ai/neo/bug-autonomous"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/bug-autonomous.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.00022 | $0.01226 |
| Opus 5 | $0.00011 | $0.00613 |
| Sonnet 5 | $0.00004 | $0.00245 |
| Haiku 4.5 | $0.00002 | $0.00123 |
Grade A, and why
bug-autonomous 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Bug Planning & Implementation
Generate a bug fix plan using multi-agent research, then implement with full validation loop.
Instructions
- You're autonomously planning and fixing a bug using Phase 0 research
- Phase 0: Use 3 agents to research and generate O1-O4 options
- CRITICAL: Phase 0 MUST output explicit Test Specification
- After planning, automatically proceed to /implement with the generated plan
Bug
$ARGUMENTS
Phase 0: PreflightExplain
Step 0.1: Parse Bug
- Extract bug description from $ARGUMENTS
- Classify severity and scope
- Define acceptance criteria (bug is fixed when...)
Step 0.2: Codebase Research
- INVOKE Task tool:
- subagent_type: "codebase-researcher"
- description: "Research codebase for bug context"
- prompt: "Research the codebase for bug: {bug_description}. Identify: (1) Files likely related to the bug, (2) Existing tests for affected code, (3) Similar bugs previously fixed, (4) Dependencies and side effects. Provide structured report with file paths and line numbers."
Step 0.3: Bug Analysis
- INVOKE Task tool:
- subagent_type: "debug-detective"
- description: "Deep bug analysis"
- prompt: "Analyze bug: {bug_description}. Investigate: (1) Root cause hypotheses, (2) Steps to reproduce, (3) Edge cases and variants, (4) Complexity assessment. Provide comprehensive analysis."
Step 0.4: Generate Fix Options
- INVOKE Task tool:
- subagent_type: "linus-kernel-planner"
- description: "Generate O1-O4 fix options"
- prompt: "Create bug fix plan for: {bug_description}. Generate exactly 4 options (O1-O4), each with: approach overview, files to modify, complexity assessment (lines changed, risk level), risks and edge cases. Include: (1) Problem Assessment, (2) Root Cause Analysis, (3) Four Fix Options with tradeoffs, (4) Recommended Solution (simplest), (5) What NOT to Do (avoid over-engineering). Reject complex solutions. Prefer surgical fixes."
Step 0.5: Synthesize Plan with Test Specification
- Compile results from all agents
- Choose simplest option (usually O1 or O2)
- Produce BugFixPlan with REQUIRED sections:
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 · 148 lines · 22 tokens per session scan A 091eb2554055
bug-autonomous is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed yesterday), licensed Apache-2.0. It adds 22 tokens to every session and 1,226 once invoked, about $0.0001 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-30.
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.