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/kid-sid/claude-spellbookWrote 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/commands/kid-sid/claude-spellbook/roast-repo)<a href="https://agentmods.dev/commands/kid-sid/claude-spellbook/roast-repo"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/roast-repo/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/commands/kid-sid/claude-spellbook/roast-repo"><img src="https://agentmods.dev/badge/commands/kid-sid/claude-spellbook/roast-repo.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.00000 | $0.01058 |
| Opus 5 | $0.00000 | $0.00529 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
roast-repo scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- `eval()`, `exec()`, `shell=True` / `child_process.exec` with non-literal input How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deliver a brutally honest, technically sharp roast of the current repository. Spot real bugs, code smells, security holes, and engineering sloppiness. Be pointed and witty, but every finding must be accurate and include a fix.
Instructions
Phase 1: Reconnaissance
- Run
git ls-filesto enumerate all tracked files. - Detect the primary language(s) from file extensions.
- Read
README.md(if present), CI config (.github/workflows/,Makefile, etc.), and package manifests (package.json,requirements.txt,go.mod,Cargo.toml, etc.). - Collect repo stats: total files, source files, test files, lines of code (
git ls-files | xargs wc -l 2>/dev/null | tail -1). - Check last 20 commit messages:
git log --oneline -20.
Phase 2: Code Quality (refactor skill patterns)
Scan source files for:
- Functions / methods longer than 30 lines
- Nesting deeper than 3 levels
- Magic numbers (bare literals that aren't 0, 1, or -1)
- Commented-out code blocks
- TODO / FIXME without a linked issue number
- Duplicate or near-duplicate logic blocks
- Boolean parameters (use named options/enums)
- God classes (> 10 methods or > 200 lines)
- Long parameter lists (> 4 params)
Phase 3: Security (security-scan skill patterns)
Scan all files for:
- Hardcoded secrets: patterns like
AKIA,sk-,ghp_,Bearer,password =,secret =,token =with string values - Private keys:
-----BEGIN (RSA|EC|OPENSSH) PRIVATE KEY----- - Connection strings with embedded credentials
eval(),exec(),shell=True/child_process.execwith non-literal input- SQL string concatenation
debug=TrueorDEBUG=Truein non-dev config files
Phase 4: Test Coverage
- Count test files vs source files. Ratio below 0.5 is suspicious.
- Flag source directories with zero corresponding test files.
- Look for test files that only test the happy path (single
assertor no edge-case names). - Flag any critical-sounding module (auth, payment, crypto) with no test file.
Phase 5: Engineering Hygiene
- Check
.gitignorefor common missing entries:.env,node_modules/,__pycache__/,*.pyc,dist/,build/,.DS_Store - Check for committed secrets or build artifacts that should be gitignored
- Check dependency versions: floating (
^,~,*,>=) vs pinned — flag if more than half are unpinned - Check commit messages for quality: one-word commits (
fix,wip,asdf,update), no conventional-commit style - Flag any file > 500 lines that isn't a lock file or generated file
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.
- 11d ago First seen · 92 lines · 0 tokens per session scan A de5b8b8e4647
roast-repo is a command published in the GitHub repository kid-sid/claude-spellbook (188 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,058 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.