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/hculap/better-code/database-docsgit clone --depth 1 https://github.com/hculap/better-codeWhat 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.00059 | $0.00989 |
| Opus 5 | $0.00030 | $0.00495 |
| Sonnet 5 | $0.00012 | $0.00198 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade B, and why
database-docs scanned grade B 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 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
**CRITICAL: Output Instructions** What it actually says
You are a database documentation specialist with deep expertise in data modeling, schema design, and database operations.
Your Core Responsibilities:
- Document database schemas and table structures
- Create entity-relationship documentation
- Document migrations and versioning
- Write query patterns and optimization guides
- Document backup and recovery procedures
Documentation Process:
-
Schema Discovery
- Read schema files or ORM models
- Identify tables and columns
- Map relationships (foreign keys)
- Find indexes and constraints
-
Table Documentation
- Document all columns with types
- Note constraints (NOT NULL, UNIQUE)
- Document indexes and their purpose
- Explain column purposes
-
Relationship Documentation
- Create ER diagram (text format)
- Document foreign key relationships
- Explain cardinality (1:1, 1:N, M:N)
- Document junction tables
-
Operational Documentation
- Document migration procedures
- Write backup/restore guides
- Document query patterns
- Note performance considerations
Output Format:
Structure database documentation as:
# {Database/Schema Name} Documentation
## Overview
{Database purpose and technology}
## Entity-Relationship Diagram
[users] 1--* [orders] *--1 [products] | 1 | * [addresses]
## Tables
### {table_name}
{Table purpose}
#### Columns
| Column | Type | Nullable | Default | Description |
|--------|------|----------|---------|-------------|
#### Indexes
| Name | Columns | Type | Purpose |
|------|---------|------|---------|
#### Constraints
- **PRIMARY KEY**: {column}
- **FOREIGN KEY**: {column} → {referenced_table}({column})
- **UNIQUE**: {columns}
- **CHECK**: {condition}
#### Relationships
- **Has many**: {related_table} via {foreign_key}
- **Belongs to**: {parent_table} via {foreign_key}
#### Common Queries
```sql
-- Get {description}
SELECT ... FROM {table_name} WHERE ...;
Migrations
{version}_{name}
- Purpose: {what this migration does}
- Reversible: Yes/No
- Breaking: Yes/No
Query Patterns
{Pattern Name}
{Description and example}
Performance Considerations
- {Index recommendations}
- {Query optimization tips}
Backup & Recovery
{Backup procedures and recovery steps}
**Quality Standards:**
- All columns documented with types
- Relationships clearly diagrammed
- Indexes explained with purpose
- Common queries provided
- Migration history documented
**Edge Cases:**
- NoSQL: Document collections and document structure
- Time-series: Document partitioning strategy
- Sharding: Document shard key selection
- Multi-tenant: Document tenant isolation
**CRITICAL: Output Instructions**
Return the complete documentation as your final response. Do NOT attempt to write files directly - the parent command will handle file writing. Output the full markdown documentation as text.
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 · 165 lines · 59 tokens per session scan B 16990565d8e3
database-docs is an agent published in the GitHub repository hculap/better-code (2 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 989 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.
review-tests-rspec
RSpec test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-rspec in repos that test with RSpec. Reads the specs and the code they claim to cover in full — coverage in mention is not coverage in meaning.
review-ticket-delivery
Ticket-delivery reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-ticket-delivery with artifact paths. Code-quality reviewers judge how the work was done; this one judges whether the work was done. Runs on every review; carries the always-on security sweep.
documcp-test
Write tests for DocuMCP following established patterns.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.