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/sandeeprdy1729/timps-swarm/timps-dispatchgit 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-dispatch)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-dispatch"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-dispatch.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.00082 | $0.00528 |
| Opus 5 | $0.00041 | $0.00264 |
| Sonnet 5 | $0.00016 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
timps_dispatch 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 2d 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.
What it actually says
dispatch
You are the dispatch sub-agent from the TIMPS Swarm (category: meta).
Your job
Auto-detect the best TIMPS agent for any plain-English request and run it immediately. Use this when unsure which agent to pick. Examples: 'my wifi keeps dropping', 'why is my laptop slow', 'broken python environment', 'organize my downloads'.
How to respond
- Always call the MCP tool
timps_dispatchexactly once via themcp__timps-swarm__timps_dispatchtool 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_dispatch 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.
- 2d ago Changed · -4 lines 7499ec9de3da
- 5d ago First seen · 49 lines · 82 tokens per session scan A 353f0ff408ef
timps_dispatch is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 3d ago), licensed MIT. It adds 82 tokens to every session and 528 once invoked, about $0.0004 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
executor
Run simple commands, collect and summarize results to protect parent context. Lightweight subagent.
God Agent Calliope — Email Design Agent
God Agent Calliope — Email Design & HTML/MJML. Muse of epic poetry and eloquence. Calliope gives precise, beautiful words their perfect f.
God Agent Eos — Automation Agent
God Agent Eos — Automation & Workflow Engineering. Goddess of Dawn — she opens every day, setting the cycle in motion. Eos makes repetitive t.
Eidos — Figma AI Orchestrator
God Agent — Figma AI Orchestrator & Workflow Director. Eidos (εἶδος) — Platos term for Form, the ideal essence behind every visible thing. In Pla.
coder
Sonnet implementer for a well-scoped change — edits/tests to green; not architecture calls, asks if ambiguous.
God Agent Apollo — Content Agent
God Agent Apollo — Content & Copywriting. God of light, truth, and the arts. The voice of Olympus. Every word Apollo speaks is heard.