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/theafh/ai-modules/wiki_fixnpx skills add theafh/ai-modules --skill wiki_fixgit clone --depth 1 https://github.com/theafh/ai-modulesWrote 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/theafh/ai-modules/wiki_fix)<a href="https://agentmods.dev/skills/theafh/ai-modules/wiki_fix"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/wiki_fix.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.00071 | $0.00545 |
| Opus 5 | $0.00036 | $0.00272 |
| Sonnet 5 | $0.00014 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00055 |
Grade A, and why
wiki_fix 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 3d 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
wiki_fix
<wiki_fix>
Front end for the auto_shaper_wiki agent. Hand the audit-and-fix loop off to the agent and surface its report to the user.
<orient_first_top>The auto_shaper_wiki agent reads $WIKI/SCHEMA.md once at the start of every audit it runs. This skill itself does no orientation — it delegates immediately — but the SCHEMA read inside the agent is non-skippable. The agent's <orient_first_top> enforces it.</orient_first_top>
Run the agent against the wiki of the current repository so it audits end to end and autonomously fixes every issue it finds. Defer all discovery, orientation, lint, semantic audit, remediation, and verification behavior to the agent.
Invoke the auto_shaper_wiki agent. The agent owns wiki discovery, orientation, assess, remediate, and verify phases. Do not duplicate its scope, re-list its checks, or narrow it unless the user supplied an explicit narrower scope.
<pass_through_user_scope>When the user supplied an additional scope qualifier (e.g., "only the procedures directory", "skip the scaffold check"), pass it to the agent as an extra instruction. Otherwise hand the agent its default full-wiki scope.</pass_through_user_scope>
<surface_report>Pass the agent's final report back to the user verbatim — the per-file change list, the final lint outcome, and any contested or contradicting pages flagged for human review.</surface_report>
Invoke the auto_shaper_wiki agent, forwarding any narrower scope the user supplied.
Return the agent's final report to the user.
<output_contract>
The agent's own final report — assess output, per-file change list, final lint outcome, and the audit complete — N issues resolved, K contested pages flagged line.
</output_contract>
</wiki_fix>
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.
- 3d ago First seen · 28 lines · 71 tokens per session scan A c25c41cf82f5
wiki_fix is a skill published in the GitHub repository theafh/ai-modules (38 stars, last pushed 4d ago), licensed MIT. It adds 71 tokens to every session and 545 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…