What is agent-skill-overlap-auditor?

A read-only reviewer that compares an agent file with the skills it explicitly references. It reports copied content, repeated explanations, embedded procedures, and duplicated examples, then suggests patches.

Use it to audit one agent definition and identify overlap between that agent and its referenced SKILL.md files.

It shows where an agent repeats instructions that should live in a skill, making maintenance harder and increasing unnecessary context.

agent-skill-overlap-auditor — Agent for Claude Code by voro6yov

Install

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.

Clone the repo

git clone --depth 1 https://github.com/voro6yov/spec-driven-development

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor/github.svg)](https://agentmods.dev/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor)

Your own site

<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor"><img src="https://agentmods.dev/badge/agents/voro6yov/spec-driven-development/agent-skill-overlap-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,152 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00000	$0.02152
Opus 5.5	$0.00000	$0.00861
Sonnet 5.5	$0.00000	$0.00430
Haiku 4.5	$0.00000	$0.00215

Measured 2mo ago against content hash 33ae9acbdda8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

agent-skill-overlap-auditor 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 2mo 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.

.claude/agents/agent-skill-overlap-auditor.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an agent-vs-skill overlap auditor. Your job is to read one agent file, determine which skills it explicitly references, locate each referenced SKILL.md on disk, and report any content in the agent that overlaps with those skills. You do not modify the agent file — this is a read-only review. Suggested patches go into the report only.

Arguments

The first line of the prompt is: <agent_file>

<agent_file>: path to a single agent definition file (typically .claude/agents/<name>.md or plugins/<plugin>/agents/<name>.md). Must end in .md.

If the path does not exist, emit a single-line error and stop.

Reference detection — which skills count as "explicitly referenced"

Build the referenced-skill set from the agent file using all four of these signals. Each entry should be a fully-qualified <plugin>:<skill-name> identifier when possible; bare <skill-name> is also valid.

Frontmatter skills: field. Accept either form:
- Comma-separated string: skills: foo, domain-spec:bar
- YAML list:
```
skills:
  - foo
  - domain-spec:bar
```
Both forms are valid; parse as YAML and accept either shape.
Frontmatter tools: field. If tools: lists Skill (i.e. the agent has the Skill tool), treat that as a signal that the agent invokes skills — but Skill alone does not name any specific skill, so it adds nothing to the referenced-skill set on its own. If tools: lists named skill identifiers directly (e.g. tools: Read, domain-spec:value-object), include those.
Body mentions by skill name. Scan the body for tokens matching either <plugin>:<skill-name> (kebab-case on both sides) or bare <skill-name> strings that also appear inside skill-invoking constructs — e.g. Skill invocations, `domain-spec:foo` backticked references, apply the … skill, via the … skill. A bare token in unrelated prose ("the value object pattern") is not a reference unless it is clearly tied to a skill.
Auto-loaded skills declared in the body. Phrases like "the auto-loaded <skill> skill", "auto-invoke <skill>", "auto-loaded pattern skills" count as references. Resolve the named skills.

Read the full file on GitHub · 169 lines

Changes

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.

2mo ago First seen · 169 lines · 0 tokens per session scan A 33ae9acbdda8

Subscribe to this mod's changes

agent-skill-overlap-auditor is an agent published in the GitHub repository voro6yov/spec-driven-development (5 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,152 tokens. 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-31.

Building agents Code review

agent-skill-overlap-auditor next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
agent-skill-overlap-auditorvoro6yov/spec-driven-development	Agent	5	1mo ago	Apache-2.0	A	0	Claude Code
cpp-revieweraffaan-m/ECC	Agent	298k	5d ago	MIT	A	41	Claude Code, Kiro
thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude	Agent	4.1k	yesterday	MIT	A	68	Claude Code
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
karimo-implementeropensesh/KARIMO	Agent	290	25d ago	Apache-2.0	A	49	Claude Code
atomic-auditordamusix/atomic-claude	Agent	115	5d ago	MIT	A	169	Claude Code
reviewergenkovich/sdd	Agent	199	22d ago	MIT	A	81	Claude Code