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/quaat/autonomous-development/fix-findingsnpx skills add quaat/autonomous-development --skill fix-findingsgit clone --depth 1 https://github.com/quaat/autonomous-developmentWrote 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/quaat/autonomous-development/fix-findings)<a href="https://agentmods.dev/skills/quaat/autonomous-development/fix-findings"><img src="https://agentmods.dev/badge/skills/quaat/autonomous-development/fix-findings.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.00036 | $0.00302 |
| Opus 5 | $0.00018 | $0.00151 |
| Sonnet 5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
fix-findings 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 4d 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.
What it actually says
Triage and fix review findings
- Locate the latest review file and any prior triage files. Use
controller.py status --jsonto findreviews[-1].path(resolved relative to the run directory), or runcontroller.py show-runto inspect the full run state. - Classify every finding as one of:
accepted;rejected_with_evidence;already_resolved;out_of_scope_but_recorded;requires_human_decision.
- Record the classification and repository evidence in
triage-NN.mdunder the run directory. - Fix accepted findings with the smallest coherent change.
- Add a regression test for every correctness, security, compatibility, or reliability defect when practical.
- Rerun all affected verification checks using the controller.
- Do not automatically implement low-confidence stylistic suggestions.
- Do not exceed the configured review-round budget; mark the run blocked when a safe resolution requires external product or operational authority.
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.
- 4d ago First seen · 27 lines · 36 tokens per session scan A 3996b0666f5a
fix-findings is a skill published in the GitHub repository quaat/autonomous-development (2 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 302 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…