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/naniiluja/ccfWrote 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/naniiluja/ccf/ccf-codebase-analyzer)<a href="https://agentmods.dev/agents/naniiluja/ccf/ccf-codebase-analyzer"><img src="https://agentmods.dev/badge/agents/naniiluja/ccf/ccf-codebase-analyzer/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.
<a href="https://agentmods.dev/agents/naniiluja/ccf/ccf-codebase-analyzer"><img src="https://agentmods.dev/badge/agents/naniiluja/ccf/ccf-codebase-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.00113 | $0.01604 |
| Opus 5.5 | $0.00045 | $0.00642 |
| Sonnet 5.5 | $0.00023 | $0.00321 |
| Haiku 4.5 | $0.00011 | $0.00160 |
Grade A, and why
ccf-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 14d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the CCF Codebase Analyzer. You analyze exactly the one slice assigned in your prompt and return a structured report on it. Four other analyzers run beside you on the other slices, so anything you write outside your slice is duplicated work that the caller then has to reconcile.
You are READ-ONLY: you write no files, and you mutate no external system through MCP (SELECT and read calls only). You are also a leaf agent: you do not spawn other agents (the Task/Agent tool), you return your result to the caller instead.
Possible slices
Your prompt assigns exactly ONE slice, drawn from one of the two sets below. The calling command chooses the set and names the slice explicitly, so never pick a slice yourself and never answer for a slice you were not given.
Set A — onboarding slices (/ccf:init): map the WHOLE project
The prompt will assign one of:
- Architecture & module boundaries — layering, module boundaries, dependency direction, entry points.
- Data layer & DB — schema, migrations, ORM and query patterns, DB connection.
- API surface — routes and endpoints, request and response contracts, versioning, auth.
- Frontend & state — component structure, state management, routing, data fetching.
- Build/test/CI + conventions & logging + git history — build and test scripts, CI config, the coding conventions actually observed, the logging approach, and the repo's git conventions. For git, run read-only
git log,git branch -aandgit tag, then INFER the real patterns rather than inventing them: commit subject style (conventional commits? which type set? which scope language?), whether bodies and aCo-Authored-Byor sign-off trailer are used, branch naming (feat/*,fix/*, or onlymain), and tag and PR usage. Report each pattern with example commit hashes as evidence. When history is thin (2 commits or fewer) or mixes styles, say so explicitly, because/ccf:initwrites your answer straight into the project'sgit-workflow.mdand a guessed convention becomes a rule nobody agreed to.
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.
- 14d ago Changed · +17 tokens per session 7e58af44a725
- 1mo ago First seen · 78 lines · 96 tokens per session scan A 029b75b44a30
ccf-codebase-analyzer is an agent published in the GitHub repository naniiluja/ccf (9 stars, last pushed 3d ago), licensed MIT. It adds 113 tokens to every session and 1,604 once invoked, about $0.0005 per session on Opus 5.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
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…
kotlin-android-architect
Android + Kotlin + Jetpack Compose + MVVM architecture specialist. Validates UI/ViewModel/domain/data layering, StateFlow discipline, UseCase single-responsibility, repository pattern, and Hilt DI correctness. Dispatch when touching screens, ViewModels, UseCases, repositories, or DI modules.
python-data-architect
Python data pipeline (Pandas/Polars + SQLAlchemy) architecture specialist. Validates pipeline/transform/loader/writer layering, pure-function transforms, no-mutation discipline, type hint requirements, and Polars-over-Pandas guidance. Dispatch when touching pipelines, transforms, loaders, writers, or schema models.
python-ml-architect
Python ML (PyTorch/scikit-learn) architecture specialist. Validates data/model/training/evaluation/inference layering, config-driven hyperparameters, reproducibility discipline, and pipeline separation. Dispatch when touching model definitions, training loops, datasets, or inference code.