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 skills add saajunaid/caddis-plugin --skill codebase-auditgit clone --depth 1 https://github.com/saajunaid/caddis-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/skills/saajunaid/caddis-plugin/codebase-audit)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/codebase-audit"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/codebase-audit/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/skills/saajunaid/caddis-plugin/codebase-audit"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/codebase-audit.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.00050 | $0.01852 |
| Opus 5.5 | $0.00020 | $0.00741 |
| Sonnet 5.5 | $0.00010 | $0.00370 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
codebase-audit 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 17d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Audit Skill
Systematic 6-step audit for entering an unfamiliar codebase before architecture changes, major features, or refactoring. Do not guess patterns — audit first.
1. When to Apply This Skill
Trigger conditions:
- "I'm new to this codebase"
- "Audit this project before we start building"
- "I need to understand what's here before changing it"
- "Pre-implementation review"
- Any major feature in a codebase you haven't worked in this session
Do not skip the audit even when the task seems small — hidden coupling causes broken assumptions.
2. Audit Scope — 20 Areas
| # | Area | What to Look For |
|---|---|---|
| 1 | Architecture | Monolith/microservice/monorepo, layer separation, module boundaries |
| 2 | Entry Points | Main files, router setup, CLI entry, exports index |
| 3 | Framework & Runtime | React version, Next.js, FastAPI, Django, Node version, Python version |
| 4 | Dependencies | package.json/pyproject.toml — packages, versions, peer deps, outdated |
| 5 | Code Quality | Lint config, formatter, TypeScript strict mode, type coverage |
| 6 | Testing | Test runner, coverage %, which layers are tested, missing tests |
| 7 | Security Posture | Auth implementation, env var usage, hardcoded secrets, CORS |
| 8 | Documentation | README completeness, inline comments, API docs |
| 9 | Performance Signals | Caching, lazy loading, database indexes, N+1 queries |
| 10 | DevOps / CI | Build commands, CI config, deployment method, Dockerfile |
| 11 | API Design | REST conventions, versioning, error response format, input validation |
| 12 | Data Layer | ORM vs raw SQL, migration strategy, schema location |
| 13 | State Management | Client state (Zustand, Redux, Context), server state (React Query) |
| 14 | Error Handling | Global error boundary, unhandled promise rejections, logging |
| 15 | Environment Config | .env.example, pydantic-settings, config validation on startup |
| 16 | Dead Code / Tech Debt | TODOs, commented-out code, unused packages, deprecated calls |
| 17 | Naming Conventions | Consistent file/folder naming, component vs module patterns |
| 18 | Shared Libraries | Utility functions, hooks, services — shared vs duplicated |
| 19 | Accessibility | ARIA usage, keyboard nav, color contrast, skip-nav |
| 20 | Observability | Logging format, tracing, health endpoints, error reporting |
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.
- 17d ago Changed · -24 tokens per session 3a8fbe2e4be6
- 1mo ago First seen · 205 lines · 74 tokens per session scan A 2b5de1d1aff5
codebase-audit is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 1,852 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
goga-discover
Interview the user relentlessly about a decision until every branch of the design tree is resolved, then record the result as a short ADR.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-task-by-specifying
Interactive task formulation from a raw request.
goga-prototype-type-detail
Per-type detailing (methods, properties, signatures) for the prototype pipeline.
goga-change-investigator
Evidence-driven root cause investigation.