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 skills/nguyenthienthanh/aura-frog/bugfix-quicknpx skills add nguyenthienthanh/aura-frog --skill bugfix-quickgit clone --depth 1 https://github.com/nguyenthienthanh/aura-frogWrote 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/skills/nguyenthienthanh/aura-frog/bugfix-quick)<a href="https://agentmods.dev/skills/nguyenthienthanh/aura-frog/bugfix-quick"><img src="https://agentmods.dev/badge/skills/nguyenthienthanh/aura-frog/bugfix-quick.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.00047 | $0.00995 |
| Opus 5 | $0.00023 | $0.00498 |
| Sonnet 5 | $0.00009 | $0.00199 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
bugfix-quick 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-consumed reference. Optimized for Claude to read during execution. Human-readable explanation: see docs/architecture/HIERARCHICAL_PLANNING.md or docs/getting-started/ depending on topic.
Quick Bugfix
For bugs only. Features/refactors → run-orchestrator.
Core Principle
NO FIXES WITHOUT ROOT CAUSE. Fix at SOURCE, not symptom.
Process (4 Steps)
| Step | Name | Agent | Statusline |
|---|---|---|---|
| S1 | Investigate | lead (inline) — uses Read/Grep/Bash to reproduce |
bugfix S1 |
| S2 | Test RED | tester — writes failing test |
bugfix S2 |
| S3 | Fix GREEN | architect / frontend / mobile (per artifact, via agent-detector) |
bugfix S3 |
| S4 | Verify | tester — runs full suite |
bugfix S4 |
Announce per step. When transitioning, surface to the user: ─── Step S{N} · {Name} ─── Dispatching {agent}…. Also update run-state.json#current_step (one of: investigate, test-red, fix-green, verify) and #active_agent so the statusline reflects reality.
1. Investigate
- Read error + stack trace
- Reproduce the bug
git log/git difffor recent changes- Trace backward: where did bad data originate?
- Context economy (
rules/core/context-economy.md) — Grep for the failing symbol first, then Read withoffset+limiton the matched lines only. Don't read the full file unless the bug spans it.
2. Write Failing Test (RED)
- Test that reproduces the bug exactly
- Pick the right layer (
skills/test-writer/SKILL.md#test-type-selection). If the bug is a UI / user-flow / auth / payment regression → e2e spec via Playwright MCP, not a unit test that won't actually reproduce it. If the bug is in pure logic → unit. The test must fail for the right reason. - User confirms test FAILS
3. Fix (GREEN)
- Minimal, focused change at root cause
- User confirms test PASSES
4. Verify
- Run full test suite — and the e2e suite if S2 wrote an e2e spec (
npx playwright test/npx cypress run). No regressions in either. - Read output, THEN claim result. "Tests passed" with no pass count =
0 tests collected= bug. - Wrong: "Should work now" / Right: "Tests pass: [output]"
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.
- 5d ago First seen · 93 lines · 47 tokens per session scan A 9c0fa18d0c4f
bugfix-quick is a skill published in the GitHub repository nguyenthienthanh/aura-frog (24 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 995 once invoked, about $0.0002 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 skills, from other repositories
openspec-plus-tdd
MANDATORY skill that activates whenever code is written to implement an OpenSpec change task. Triggers: openspec-plus-apply is active, /opsx-apply is running, the user is implementing tasks from an OpenSpec change, an implementer subagent dispatched by openspec-plus-apply is starting work, or the user invokes phrases…
vitest-standard
Comprehensive unit testing expertise covering Vitest, test-driven development (TDD), mocking strategies, and production-grade best practices. Activates ONLY for unit testing scope (unit tests, integration tests, Vitest, TDD, Red-Green-Refactor, mocking, stubbing, spying, test coverage, and test architecture in…
tdd
Test-driven development with red-green-refactor loops around vertical slices (tracer bullets), not horizontal layers. Use when asked to "use TDD", "write test-first", "red-green-refactor", "build this with tests", or when a feature has a clear observable contract. The discipline complement to the test/add-tests skills…
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
openspec-plus-apply
MANDATORY skill that activates whenever the OpenSpec apply phase begins. Triggers: /opsx-apply runs, the openspec-apply-change vanilla skill is referenced or active, openspec instructions apply is invoked, or the user asks to implement, apply, execute, or build out an OpenSpec change ('implement the change', 'apply…
openspec-plus-proposal
MANDATORY skill that activates whenever the OpenSpec proposal phase begins. Triggers: /opsx-new or /opsx-continue runs; openspec-new-change, openspec-continue-change, or openspec-explore is active; openspec instructions proposal is invoked; or the user wants to create, update, review, refine, or discuss an OpenSpec…