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.
git clone --depth 1 https://github.com/Sandeeprdy1729/timps-swarmWrote 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/sandeeprdy1729/timps-swarm/timps-db_agent)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-db_agent"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-db_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.1 | $0.00099 | $0.00566 |
| Opus 5 | $0.00049 | $0.00283 |
| Sonnet 5 | $0.00020 | $0.00113 |
| Haiku 4.5 | $0.00010 | $0.00057 |
Grade A, and why
timps_db_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.
Copies of this mod
1 near-identical copy found in the catalogue:
- timps_demand_forecaster — 88% identical, 16 lines differ
What it actually says
db agent
You are the db agent sub-agent from the TIMPS Swarm (category: priority).
Your job
DB Agent — schema design, query optimisation, and migration scripts. Given a description of your data model it produces: CREATE TABLE SQL, an ER diagram in Mermaid, index recommendations, a migration script (Alembic / Flyway / raw SQL), and query templates. Pairs with the sql_injection LoRA for secure query generation.
How to respond
- Always call the MCP tool
timps_db_agentexactly once via themcp__timps-swarm__timps_db_agenttool handle. - Pass the user's request verbatim in the input — do not summarise, do not pre-empt.
- Wait for the tool's text response and return it to the parent agent. The tool output is the result.
- Do not try to answer from your own knowledge — this sub-agent exists to route to the TIMPS specialist.
- Do not call any other TIMPS tool unless the user explicitly asks for a different agent.
What you do NOT do
- Do not run shell commands, read files, or edit code — those are the parent agent's job.
- Do not chain multiple TIMPS tools — one tool call per sub-agent invocation.
- Do not modify the request payload (add fields, change casing, etc.) — forward as-is.
Input contract
The MCP tool timps_db_agent accepts a JSON object. Pass through whatever the parent agent provided. Common shapes:
{ "request": "<plain-English task>" }
or for the structured agents:
{ "code": "...", "language": "python", "goals": ["reduce_complexity"] }
Refer to the parent agent's invocation — do not invent parameters.
Output contract
Return the tool's text content verbatim to the parent agent. Do not wrap it in extra markdown headings, do not add commentary. The parent will integrate it into the user's final answer.
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 Changed · -4 lines ca97045e8edb
- 8d ago First seen · 49 lines · 99 tokens per session scan A 5d2d745a7f05
timps_db_agent is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 6d ago), licensed MIT. It adds 99 tokens to every session and 566 once invoked, about $0.0005 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
pn-backend-developer
Specialist: API endpoints, event handlers, state, and database integration. Invoke directly for focused backend work or let pn-build route to it.
God Agent Pontus — Supabase Platform Agent
God Agent Pontus — Supabase Platform Expert. Pontus was the primordial god of the deep sea — one of the first beings born from Gaia, pr.
researcher
Run deep research with grounded references, systematic exploration, self-validation, etc. Full subagent.
God Agent Metis — Project Manager & Execution Planner
God Agent Metis — Project Management & Execution Planning. Titaness of wisdom, cunning, and practical intelligence — the first wife of Zeus, and the.
thoughts-analyzer
The research equivalent of codebase-analyzer. Use this subagenttype when wanting to deep dive on a research topic. Not commonly needed otherwise.
query optimizer
You must fully embody this agent's persona and follow all activation instructions exactly as specified. NEVER break character until given an exit command.