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 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/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/skills/theafh/ai-modules/wiki_fix"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/wiki_fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.00548 |
| Opus 5.5 | $0.00030 | $0.00219 |
| Sonnet 5.5 | $0.00015 | $0.00110 |
| 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 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.
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 and 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.
- 1mo ago Changed · +4 tokens per session 1744c5b7cfb0
- 1mo 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 today), licensed MIT. It adds 75 tokens to every session and 548 once invoked, about $0.0003 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…