mcpbeat

Module Audit Agent

wednesday-solutions/module-audit-agent

Use when asked to audit a module, check its health, or assess whether it should be refactored. Runs structural query, risk check, and test generation automatically.

505 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
164
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/wednesday-solutions/ai-agent-skills --skill module-audit-agent

The instruction itself

4 sections, as written by the author

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.json and summaries.json for the target module. Report: what it does, its imports, what imports it, and any known conflicts.
  • brownfield-fix — Run wednesday-skills score <module> and wednesday-skills blast <module>. Report risk band and total dependent count.
  • 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

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

How to use it

Copy the folder

Take wednesday-solutions/module-audit-agent from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.