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/vedanta/the-system/database-developergit clone --depth 1 https://github.com/vedanta/the-systemWhat 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.00027 | $0.06492 |
| Opus 5 | $0.00014 | $0.03246 |
| Sonnet 5 | $0.00005 | $0.01298 |
| Haiku 4.5 | $0.00003 | $0.00649 |
Grade A, and why
database-developer 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 yesterday.
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.
The source is not reproduced here
Licensed LGPL-3.0
The repository is licensed LGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday First seen · 1,017 lines · 27 tokens per session scan A 36dc4176c6f1
database-developer is an agent published in the GitHub repository vedanta/the-system (9 stars, last pushed 5mo ago), licensed LGPL-3.0. It adds 27 tokens to every session and 6,492 once invoked, about $0.0001 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-31.
Other agents, from other repositories
library_book_renewal.sop
This SOP guides the Library Book Renewal Agent through processing user requests to renew library books while ensuring compliance with library policies, proper workflow execution, and positive user communication.
huyen-agents
Updated 2025: This is a summary of Chip Huyen's blog and book chapter on agents, with some added context to provide a comprehensive overview of their design, capabilities, and practical applications.
README
This directory contains the 12 Claude Code agents that implement the SpecRoute skeleton. They are project-internal - they build SpecRoute itself, not consumer-facing templates that ship as artifacts.
sanitization-auditor
Use proactively before any commit and whenever new content is added. Scans tracked files for private-project leaks - upstream private project names, internal absolute paths, proprietary domain logic (financial / portfolio / trading / prediction / tax / advisory specifics), customer data, secrets, internal endpoints…
roster
Cross-vendor inventory of agents for a SpecRoute-driven project. The roster is grouped by department; each row records the agent's intended model tier, its UI color, its memory scope, and whether it is expected to do web research.
agent-roster-architect
Use when designing or extending the consumer-facing agent roster under agents/. Owns agents/agent-template.md (frontmatter contract), agents/archetypes/ (role concepts - product, architect, backend, frontend, security, qa, devops), agents/examples/ (flat .md files showing real frontmatter shape), and agents/roster.md…