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/melodic-software/claude-code-plugins/audit-automation-gapsnpx skills add melodic-software/claude-code-plugins --skill audit-automation-gapsgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWrote 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/melodic-software/claude-code-plugins/audit-automation-gaps)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/audit-automation-gaps"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/audit-automation-gaps.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.00126 | $0.02663 |
| Opus 5 | $0.00063 | $0.01332 |
| Sonnet 5 | $0.00025 | $0.00533 |
| Haiku 4.5 | $0.00013 | $0.00266 |
Grade A, and why
audit-automation-gaps 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Automation inventory: !bash "${CLAUDE_PLUGIN_ROOT}/skills/audit-automation-gaps/scripts/inventory.sh" 2>/dev/null || echo "inventory unavailable"
Purpose
Audit the repo's automation landscape and identify genuine gaps, not surface-level "you don't have X" observations, but evidence-backed gaps where no mechanism in the enforcement hierarchy covers the concern.
Design principle: most "missing automation" gaps are already covered by higher enforcement levels (compiler, analyzers, build-time checks, architecture tests, behavioral rules). This skill's job is to prove a gap exists before recommending a solution. The default verdict is REJECT, not PASS.
The enforcement hierarchy (strongest first): compiler settings → static analyzers/linters →
architecture tests → unit/integration tests → git hooks → Claude Code hooks → code review →
documentation/behavioral rules. A consuming repo that documents its own hierarchy in CLAUDE.md or
rules files overrides this default ordering, so read and use theirs.
Adapting to your environment (graceful degrade)
This skill is self-contained. Where a phase names an adjacent capability, such as a research skill, an
implementation-planning skill, a work-item tracker, or an outcome verifier, treat it as optional: if
your setup provides an equivalent, use it; otherwise follow the inline guidance, which stands on its
own. Adjacent skills cover neighboring questions: the sibling audit skill (are the config FILES
correct?) and the audit skill in the claude-memory plugin (is the instruction layer healthy?).
Arguments
Parse $ARGUMENTS for:
--recommend-only: Run evaluation phases only, skipping implementation. Default behavior--implement: After presenting validated recommendations, implement user-chosen items sequentially- Category filter (
hooks,mcp,skills,subagents,scheduled): Limit to a specific automation type. Default:all
Track progress
For any deep-dive run (Phases 1-4), keep a phase checklist and tick each phase + every anti-noise
doctrine check as it completes, either in-response or by copying
${CLAUDE_PLUGIN_ROOT}/skills/audit-automation-gaps/templates/checklist.md into wherever the consuming
repo keeps working task notes. Phase 4 is SKIPPED in default --recommend-only mode.
What ships with it
5 files 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.
- 3d ago First seen · 211 lines · 126 tokens per session scan A a83a2fef9637
audit-automation-gaps is a skill published in the GitHub repository melodic-software/claude-code-plugins (14 stars, last pushed today), licensed MIT. It adds 126 tokens to every session and 2,663 once invoked, about $0.0006 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
content-distribution
Generate and distribute value-first content across all channels: Dev.to, Hashnode, Medium, Hackernoon, Substack, Hacker News, Claude Discord, LinkedIn, Reddit, email, and landing pages. Shares expert Claude Code marketplace knowledge. Includes channel-specific templates, day-of-week rotation, and identity-aligned…
daily-crm-brief
The morning CRM briefing. Orchestrates pipeline-tracker + hypothesis-ledger into a single actionable brief: pipeline snapshot, hot leads, overdue follow-ups, email drafts to review, and all effective copy-paste-ready actions for Ed (minimum 3, no cap) — each tagged with a new [C-###] hypothesis. Load crm-identity…
lead-enrichment
World-class lead enrichment using 7 data sources: Gmail threads, GitHub profile, web search, company website, email domain analysis, internal CRM cross-reference, and website analytics. Builds a complete picture of who we're selling to.
crm-identity
CRM identity and definitions for systemprompt.io. Defines pipeline stages, lead scoring rubric, email rules, and integration with marketing. Load FIRST before any other crm skill.
email-composer
Draft and send CRM emails via the Resend API. Loads templates from reports/crm/templates/, personalises with lead context, presents draft for MANDATORY human approval, then sends via curl. Every email requires Ed's explicit approval before sending — no exceptions.
changelog-summarizing
Use this skill when the user asks to summarize, recap, or post about repository changes in the Shopware AI Coding Tools marketplace since a given date — phrases like "write a changelog post for Discord", "recap this week's commits for Slack", "summarize what shipped since 2026-04-01", "draft a release announcement".…