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 agentmods add agents/jayminwest/kotadb/readmegit 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/agents/jayminwest/kotadb/readme)<a href="https://agentmods.dev/agents/jayminwest/kotadb/readme"><img src="https://agentmods.dev/badge/agents/jayminwest/kotadb/readme.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 | $0.00000 | $0.01150 |
| Opus 5 | $0.00000 | $0.00575 |
| Sonnet 5 | $0.00000 | $0.00230 |
| Haiku 4.5 | $0.00000 | $0.00115 |
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 4d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Agents
This directory contains agent definitions for Claude Code. Agents are specialized configurations that define tool access, capabilities, and behavioral constraints for specific use cases.
Agent Structure
Each agent definition follows a standard frontmatter format:
---
name: agent-name
description: Brief description of agent purpose
tools:
- Tool1
- Tool2
model: haiku|sonnet|opus
constraints:
- Constraint description
---
Available Agents
Core Agents
| Agent | Purpose | Tool Access | Model |
|---|---|---|---|
| scout-agent | Read-only codebase exploration | Glob, Grep, Read, MCP search | haiku |
| build-agent | File implementation and modification | Edit, Write, Bash, full toolset | sonnet |
| review-agent | Code review and analysis | Read-only + review-focused tools | haiku |
| docs-scraper | Documentation scraping and saving | WebFetch, Firecrawl, Write | sonnet |
Expert Domains (4-Agent Pattern)
Expert domains provide structured expertise with a consistent 4-agent workflow: plan -> build -> improve -> question.
| Domain | Purpose | Location |
|---|---|---|
| claude-config | .claude/ configuration management (commands, hooks, settings) | experts/claude-config/ |
| agent-authoring | Agent creation and modification (frontmatter, tools, registry) | experts/agent-authoring/ |
Each domain includes:
- plan-agent: Creates implementation specs and plans
- build-agent: Implements changes based on specs
- improve-agent: Evolves expertise and refines implementations
- question-agent: Answers questions (read-only, no approval needed)
Agent Registry
For programmatic access to agent definitions, use agent-registry.json:
{
"agents": { ... }, // Agent definitions with tools and capabilities
"capabilityIndex": { ... }, // Map capabilities to agent IDs
"modelIndex": { ... }, // Map model tiers to agent IDs
"toolMatrix": { ... } // Map tools to agents that use them
}
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.
- 4d ago First seen · 140 lines · 0 tokens per session scan A d963b45536d2
README is an agent published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,150 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 agents, from other repositories
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
cursor-rescue
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Cursor.
security-reviewer
인증, 권한, 결제, 데이터 삭제, 외부 입력 처리 변경 전후에 사용한다.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.