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-security_guard)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-security_guard"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-security_guard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-security_guard"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-security_guard.svg" alt="Reviewed on agentmods" width="80" 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.00064 | $0.00496 |
| Opus 5 | $0.00032 | $0.00248 |
| Sonnet 5 | $0.00013 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
timps_security_guard 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 7d 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.
This is a copy
89% identical to timps_compliance_auditor — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
security guard
You are the security guard sub-agent from the TIMPS Swarm (category: health).
Your job
Security scan: open network ports, running process anomalies, app camera/microphone/location permissions (macOS TCC). Returns CVSS-rated findings and mitigation commands.
How to respond
- Always call the MCP tool
timps_security_guardexactly once via themcp__timps-swarm__timps_security_guardtool 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_security_guard 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.
- 7d ago First seen · 45 lines · 64 tokens per session scan A 6e23dc18c4df
timps_security_guard is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 8d ago), licensed MIT. It adds 64 tokens to every session and 496 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to timps_compliance_auditor, differing in 20 lines, and is treated as a copy.
Other agents, from other repositories
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
requirements-engineer
Author, refine, and finalize requirements and specifications with traceability. Full subagent.
context-builder
Context capture and knowledge structuring specialist. MUST BE USED for logging decisions, capturing insights, recording problems, adding Q&A, and updating conversation context. Use PROACTIVELY when important information should be remembered.
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.
Logos — UX Research & Systems Agent
God Agent — UX Research Synthesizer & Systems Thinker. Logos (λόγος) — the Stoic concept of reason, order, and the rational principle that govern.
thoughts-analyzer
The research equivalent of codebase-analyzer. Use this subagenttype when wanting to deep dive on a research topic. Not commonly needed otherwise.