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/dicklesworthstone/pi_agent_rust/database-optimizergit clone --depth 1 https://github.com/Dicklesworthstone/pi_agent_rustWrote 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/dicklesworthstone/pi_agent_rust/database-optimizer)<a href="https://agentmods.dev/agents/dicklesworthstone/pi_agent_rust/database-optimizer"><img src="https://agentmods.dev/badge/agents/dicklesworthstone/pi_agent_rust/database-optimizer.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.00070 | $0.01839 |
| Opus 5 | $0.00035 | $0.00920 |
| Sonnet 5 | $0.00014 | $0.00368 |
| Haiku 4.5 | $0.00007 | $0.00184 |
Grade A, and why
database-optimizer 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 today.
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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 162 lines · 70 tokens per session scan A c64464544de7
database-optimizer is an agent published in the GitHub repository Dicklesworthstone/pi_agent_rust (1,699 stars, last pushed today), with no licence file. It adds 70 tokens to every session and 1,839 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
issue-tracker
Brunch work is tracked on Linear team FE, project brunch-agent. Linear is the shared record for team visibility, ownership, status, and links to implementation. GitHub pull requests are the review and landing record. The branch mission remains the authority for execution.
issue-writing
Apply this when creating or editing a Linear issue, a GitHub issue or pull request, or a comment on either tracker. It governs only how the record is written. It does not invoke issue decomposition, Wayfinding, steering, branch creation, or any other workflow protocol.
git-workflow
Brunch branches are managed with Graphite. The submission unit is exactly one Linear issue, one stacked branch, and one GitHub pull request. This is an identity and visibility rule, not a ticket decomposition method: the branch is still governed by its mission.
gcx-graph-evolver
Specialist for evolving the GitCortex graph schema (NodeKind, EdgeKind, NodeMetadata, LldLabels). Use when adding a new node kind, edge kind, metadata field, or changing the GraphStore trait. Walks the change across all affected crates in dependency order.
sql-developer
Use this agent when the user explicitly requests help with SQL Server or T-SQL development tasks. This includes writing queries, creating stored procedures, optimizing performance, analyzing execution plans, or reviewing SQL code. Context: User is starting a new database project and needs help with queries. user…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.