Borrowing it
Nothing to install: this file belongs to jayminwest/kotadb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jayminwest/kotadb/develop/.claude/commands/README.mdgit clone --depth 1 https://github.com/jayminwest/kotadbWrote 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/jayminwest/kotadb/readme)<a href="https://agentmods.dev/commands/jayminwest/kotadb/readme"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/readme/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/jayminwest/kotadb/readme"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/readme.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.02730 |
| Opus 5.5 | $0.00000 | $0.01092 |
| Sonnet 5.5 | $0.00000 | $0.00546 |
| Haiku 4.5 | $0.00000 | $0.00273 |
Grade A, and why
README 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 1mo 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Slash Commands
This directory contains slash command templates for Claude Code integration. Commands are organized into logical subdirectories based on their functional domain.
Template Categories
All slash commands are classified into one of four template categories based on their output requirements:
| Category | Description | Output Format | Sentinel Value |
|---|---|---|---|
| Message-Only | Returns a single piece of text | Single line or short paragraph | 0 for failure |
| Path Resolution | Returns a file path or URL | Absolute path or URL string | 0 for not found |
| Action | Performs operations, returns summary | Structured report or status | Exit code |
| Structured Data | Returns machine-parseable data | JSON object/array | Empty object/array |
Category Guidelines
Message-Only commands:
- Output must be a direct answer with no preamble
- No markdown formatting unless explicitly required
- Use
0to indicate failure or no result
Path Resolution commands:
- Output must be a valid filesystem path or URL
- Use
0when path/URL cannot be determined - No explanatory text around the path
Action commands:
- Perform side effects (file modification, git operations, etc.)
- Return structured status report
- Include validation results when applicable
Structured Data commands:
- Output must be valid JSON
- Follow documented schema
- Return empty array
[]or object{}for no results
Meta-Commentary Patterns (FORBIDDEN)
These patterns are forbidden in command output across all categories:
- "Based on the changes..."
- "The commit should..."
- "Here is the..."
- "This commit..."
- "I can see that..."
- "Looking at..."
- "The changes..."
- "Let me..."
Use direct statements instead of meta-commentary.
Directory Structure
The commands are organized into the following subdirectories:
- git/ - Version control operations (commit, pull request)
- issues/ - GitHub issue template commands (feature, bug, chore, refactor, classify, audit, prioritize)
- docs/ - Documentation helpers (load AI docs)
- tools/ - Utility commands (install, tools)
- release/ - Release management commands
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.
- 1mo ago First seen · 285 lines · 0 tokens per session scan A 90ec84fca8cd
README is a command published in the GitHub repository jayminwest/kotadb (100 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,730 tokens. 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 commands, from other repositories
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
tdd-feature
Implement a new feature using full TDD loop.
auditoria-legal
Grupo: Trabajo con el framework En una frase: Auditoría de cumplimiento legal del producto — territorio, evidencia y lo que el código no cubre. Cuándo: Antes de publicar una app o web: registro, cookies, analítica, emails, suscripciones, contenido de usuarios. Quién: Cualquier operador del repo.