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 agents/ibrain-bvba/gutt-claude-code-plugin/config-discoverygit clone --depth 1 https://github.com/iBrain-BVBA/gutt-claude-code-pluginWrote 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/agents/ibrain-bvba/gutt-claude-code-plugin/config-discovery)<a href="https://agentmods.dev/agents/ibrain-bvba/gutt-claude-code-plugin/config-discovery"><img src="https://agentmods.dev/badge/agents/ibrain-bvba/gutt-claude-code-plugin/config-discovery.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.00018 | $0.00885 |
| Opus 5 | $0.00009 | $0.00443 |
| Sonnet 5 | $0.00004 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
config-discovery 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 4d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Config Discovery Agent
Scans repositories for Claude Code configurations to create a unified view of organizational tooling and identify standardization opportunities.
Trigger
- Auditing Claude Code setup across multiple repositories
- Identifying configuration drift between projects
- Finding standardization opportunities
- Creating inventory of skills, agents, hooks, and MCP servers
Discovery Targets
Configuration Files
| File | Purpose |
|---|---|
.claude/settings.json |
Hooks, permissions, MCP servers |
.mcp.json |
MCP server configurations |
CLAUDE.md |
Project instructions |
Components
| Directory | Contents |
|---|---|
.claude/hooks/ |
Hook scripts (.cjs, .js) |
.claude/skills/ |
Skill definitions (SKILL.md) |
.claude/agents/ |
Agent definitions (.md) |
.claude/commands/ |
Custom commands (.md) |
Discovery Workflow
Step 1: Identify Repositories
# From configured list or scan directory
ls ~/dev/*/CLAUDE.md 2>/dev/null
Step 2: Scan Each Repository
For each repo, discover:
- Hooks: count and names
- Skills: count and names
- Agents: count and names
- MCP servers: configurations
Step 3: Compare Configurations
Identify:
- Drift: Same component, different implementations
- Gaps: Missing components
- Outdated: Older versions
Step 4: Generate Report
Output markdown with:
- Repository inventory
- Configuration comparison
- Inconsistencies found
- Recommendations
Output Format
# Config Discovery Report
## Repository Inventory
| Repository | Hooks | Skills | Agents | MCP Servers |
| ---------- | ----- | ------ | ------ | ----------- |
| gutt-pro | 3 | 5 | 9 | 2 |
| cc-sales | 2 | 3 | 4 | 1 |
## MCP Servers in Use
| Server | Repos Using |
| --------------- | ----------- |
| gutt-pro-memory | 3 |
| atlassian | 2 |
## Inconsistencies Found
1. Hook `post-tool-lint` differs between repos
2. Skill `memory-retrieval` outdated in platform
## Recommendations
1. Install gutt-pro in all repos
2. Update outdated components
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.
- 4d ago First seen · 147 lines · 18 tokens per session scan A cfdcf5a1cca8
config-discovery is an agent published in the GitHub repository iBrain-BVBA/gutt-claude-code-plugin (5 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 885 once invoked, about $0.0001 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.