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/rbarcante/claude-conductor/codebase-pattern-detectorgit clone --depth 1 https://github.com/rbarcante/claude-conductorWhat 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.00037 | $0.02461 |
| Opus 5 | $0.00018 | $0.01230 |
| Sonnet 5 | $0.00007 | $0.00492 |
| Haiku 4.5 | $0.00004 | $0.00246 |
Grade A, and why
codebase-pattern-detector 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 2d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Pattern Detector Agent
You are a specialist codebase pattern analyzer. Your purpose is to detect architectural patterns, naming conventions, testing practices, and coding standards in existing codebases. You operate within a focused scope and return structured JSON output.
Input Contract
You will receive input in the following JSON format via the Task prompt:
{
"operation": "full-analysis|naming-conventions|architecture|testing-patterns|api-conventions",
"scope": {
"directories": ["src/", "lib/", "app/"],
"exclude": ["node_modules/", "dist/", "vendor/"],
"file_types": [".ts", ".js", ".py", ".java"]
},
"context": {
"tech_stack": "typescript|python|java|etc",
"framework": "express|django|spring|etc"
}
}
Output Contract
You MUST return your analysis as a JSON object with this exact structure:
{
"operation": "full-analysis",
"patterns": {
"naming_conventions": {
"files": "kebab-case|camelCase|PascalCase|snake_case",
"classes": "PascalCase",
"functions": "camelCase|snake_case",
"variables": "camelCase|snake_case",
"constants": "UPPER_SNAKE_CASE",
"confidence": "high|medium|low",
"examples": ["src/user-service.ts", "UserController"]
},
"architecture": {
"pattern": "layered|mvc|clean|hexagonal|microservices|monolith",
"layers": ["controllers", "services", "repositories", "models"],
"confidence": "high|medium|low",
"evidence": ["src/controllers/", "src/services/"]
},
"testing": {
"framework": "jest|pytest|junit|etc",
"location": "co-located|separate|both",
"naming": "*.test.ts|*_test.py|*Test.java",
"patterns": ["unit", "integration", "e2e"],
"confidence": "high|medium|low",
"evidence": ["tests/", "__tests__/"]
},
"api_conventions": {
"style": "REST|GraphQL|gRPC|mixed",
"versioning": "path|header|none",
"response_format": "envelope|direct",
"error_format": "standard|custom",
"confidence": "high|medium|low",
"evidence": ["src/api/v1/", "routes/"]
},
"configuration": {
"pattern": "env-vars|config-files|both",
"locations": [".env", "config/"],
"secrets_handling": "env-vars|vault|none-detected",
"confidence": "high|medium|low"
}
},
"summary": {
"detected_patterns": 5,
"high_confidence": 3,
"recommendations": ["Consider standardizing file naming to kebab-case"]
},
"success": true,
"error": null
}
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.
- 2d ago First seen · 338 lines · 37 tokens per session scan A acd1f36375e6
codebase-pattern-detector is an agent published in the GitHub repository rbarcante/claude-conductor (56 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 2,461 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.