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 wednesday-solutions/ai-agent-skills --skill module-auditgit clone --depth 1 https://github.com/wednesday-solutions/ai-agent-skillsWrote 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/wednesday-solutions/ai-agent-skills/module-audit)<a href="https://agentmods.dev/skills/wednesday-solutions/ai-agent-skills/module-audit"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/module-audit/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/wednesday-solutions/ai-agent-skills/module-audit"><img src="https://agentmods.dev/badge/skills/wednesday-solutions/ai-agent-skills/module-audit.svg" alt="Reviewed on agentmods" width="80" 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.00039 | $0.00438 |
| Opus 5 | $0.00019 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
module-audit-agent 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 10d 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
Module Audit Agent
When to use
- "Audit this module"
- "Is it safe to refactor X?"
- "What is the health of this service?"
- "Should we rewrite X?"
What to do
-
In parallel:
- brownfield-chat — Read
dep-graph.jsonandsummaries.jsonfor the target module. Report: what it does, its imports, what imports it, and any known conflicts. - brownfield-fix — Run
wednesday-skills score <module>andwednesday-skills blast <module>. Report risk band and total dependent count.
- brownfield-chat — Read
-
Present the combined audit report:
- Purpose summary (from summaries.json)
- Risk score + band (0–30 low / 31–60 medium / 61–80 high / 81–100 critical)
- Blast radius (dependent count, cross-language flagged separately)
- Architecture violations or danger zone warnings (from MASTER.md)
- Recommendation: proceed / review / senior sign-off / do not touch
-
brownfield-tests — Only run if coverage < 30% AND risk > 50:
- Run
wednesday-skills gen-tests --file <module> - Show generated test file to dev for review before writing
- Run
Never
- Recommend refactoring a critical file (risk > 80) without flagging the blast radius
- Read raw source to answer structural questions — use graph only
- Auto-write test files without showing the dev first
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 47 lines · 39 tokens per session scan A 601ce57a77fc
module-audit-agent is a skill published in the GitHub repository wednesday-solutions/ai-agent-skills (168 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 438 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
issue-root-resolution
Trigger: root audit, atacar la raíz, issue roots, backlog roots, mechanism map, deletion-driven fix, resolver issues de raíz, close outdated issues. Audit and resolve issue clusters by verified root cause.
rdd-defect-workflow
Trigger: RDD, receipt-driven development, review authority, receipt/lineage, correction/recovery, delivery gate/kill switch, bounded review defects. Guide work.
incident-response
Incident management lifecycle — triage, communicate, mitigate, postmortem. Three modes — new (start incident), update (status update), postmortem (blameless RCA report).
discover
Primary router for discovery, debugging, investigation, quality, and exploration workflows. Analyzes user intent and dispatches to debug, bughunt, quick-review, deep-review, coverage, testing-strategy, learn, tour, impact, assist-review. The recommended entry point for any 'find out', 'check', 'review', or…
mattpocock-dev-workflows
Use when you need Matt Pocock's engineering workflow patterns: spec synthesis, deep-module design, domain modeling, two-axis code review, or disciplined bug diagnosis. A meta-skill covering five complementary sub-patterns for real engineering — not vibe coding.