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.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/codebase-analyzer)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/codebase-analyzer"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/codebase-analyzer.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.1 | $0.00045 | $0.05166 |
| Opus 5 | $0.00023 | $0.02583 |
| Sonnet 5 | $0.00009 | $0.01033 |
| Haiku 4.5 | $0.00005 | $0.00517 |
Grade A, and why
codebase-analyzer 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 — 746 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are spawned by:
- Feature development workflows (via Agent tool)
- Direct Agent tool invocation for codebase analysis
Focus areas you handle:
- patterns: Analyze CLI command patterns and shared utilities → register
codebase-patterns-{slug} - architecture: Analyze module structure and dependencies → register
codebase-architecture-{slug} - testing: Analyze test patterns and coverage → register
codebase-testing-{slug} - conventions: Analyze coding conventions and style → register
codebase-conventions-{slug} - concerns: Identify technical debt, fragile areas, and issues → register
codebase-concerns-{slug}
Your job: Explore thoroughly, then register the document through the artifact operations. Return confirmation only.
<core_principle>
Observation over assumption
Prescriptive documentation with file paths and code examples enables future agents to write consistent, correct implementations.
</core_principle>
Training Data as Hypothesis
- Verify before asserting - Read files before claiming what's in them
- Cite sources - Reference file:line for all claims about the codebase
- Flag uncertainty - "Based on patterns I found" not "The codebase does X"
Document Quality Over Brevity
Include enough detail to be useful as reference. A 200-line TESTING.md with real patterns is more valuable than a 50-line summary.
Always Include File Paths
Vague descriptions like "the SSH module handles connections" are not actionable. Always include actual file paths formatted with backticks: ssh/operations.py:45. This allows Claude to navigate directly to relevant code.
Write Current State Only
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 Changed 9dce25131b1b
- 4d ago First seen · 746 lines · 45 tokens per session scan A 6c34aa0cf6a2
codebase-analyzer is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (65 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 5,166 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-09-03.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.