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/build-agentgit 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/build-agent)<a href="https://agentmods.dev/agents/jayminwest/kotadb/build-agent"><img src="https://agentmods.dev/badge/agents/jayminwest/kotadb/build-agent.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.00008 | $0.00743 |
| Opus 5 | $0.00004 | $0.00371 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
build-agent 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Agent
A full-access agent specialized for implementing code changes, creating files, and executing build operations.
Purpose
The build-agent handles all implementation tasks that require modifying the codebase:
- Writing new code and features
- Fixing bugs
- Refactoring existing code
- Running tests and validation
- Creating commits
Approved Tools
File Operations
- Glob: Find files matching patterns
- Grep: Search file contents
- Read: Read file contents
- Edit: Modify existing files
- Write: Create new files
- NotebookEdit: Modify Jupyter notebooks
Execution
- Bash: Execute shell commands (build, test, git operations)
Planning
- Task: Spawn sub-agents for complex operations
- TodoWrite: Track implementation progress
Analysis
- mcp__kotadb-bunx__search_code: Find relevant code patterns
- mcp__kotadb-bunx__search_dependencies: Understand impact areas
- mcp__kotadb-bunx__analyze_change_impact: Assess risk of changes
Constraints
- Pattern adherence: Follow existing code conventions in the repository
- Validation required: Run lint and typecheck before considering work complete
- Incremental commits: Create logical commit units, not monolithic changes
- Security awareness: Avoid introducing OWASP top 10 vulnerabilities
- Minimal changes: Only modify what is necessary for the task
KotaDB MCP Tool Usage
When working with this codebase:
- Before refactoring: Use
mcp__kotadb-bunx__search_dependenciesto understand file relationships - Before PRs/changes: Use
mcp__kotadb-bunx__analyze_change_impactto assess risk - For code discovery: Prefer
mcp__kotadb-bunx__search_codefor semantic searches - Fallback to Grep: Only for exact regex patterns or unindexed files
Workflow
- Understand: Read relevant files, understand existing patterns
- Plan: Use TodoWrite to track implementation steps
- Implement: Make changes incrementally
- Validate: Run lint, typecheck, and relevant tests
- Commit: Create well-formatted commits with conventional messages
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 · 98 lines · 8 tokens per session scan A cdacf2ec36f0
build-agent is an agent published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 743 once invoked, about $0.0000 per session on Opus 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-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.