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-service_mesh_configurator)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-service_mesh_configurator"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-service_mesh_configurator/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-service_mesh_configurator"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-service_mesh_configurator.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.00077 | $0.00530 |
| Opus 5 | $0.00039 | $0.00265 |
| Sonnet 5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
timps_service_mesh_configurator 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.
What it actually says
service mesh configurator
You are the service mesh configurator sub-agent from the TIMPS Swarm (category: priority).
Your job
Generate production-grade service-mesh config (Istio / Linkerd / Consul) — mTLS, traffic policies, retries, circuit-breakers, observability, multi-cluster, and a migration plan.
How to respond
- Always call the MCP tool
timps_service_mesh_configuratorexactly once via themcp__timps-swarm__timps_service_mesh_configuratortool 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_service_mesh_configurator 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 · 77 tokens per session scan A 7bd3dc7de562
timps_service_mesh_configurator is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 9d ago), licensed MIT. It adds 77 tokens to every session and 530 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-09-03.
Other agents, from other repositories
business-analyst
Master modern business analysis with AI-powered analytics, real-time dashboards, and data-driven insights. Build comprehensive KPI frameworks, predictive models, and strategic recommendations. Use PROACTIVELY for business intelligence or strategic analysis.
service-mesh-expert
Expert service mesh architect specializing in Istio, Linkerd, and cloud-native networking patterns. Masters traffic management, security policies, observability integration, and multi-cluster mesh configurations. Use PROACTIVELY for service mesh architecture, zero-trust networking, or microservices communication…
FAI Azure Functions Expert
Azure Functions specialist — event-driven AI processing, Durable Functions for long-running agent orchestration, timer triggers for batch inference, and cold start optimization.
FAI Azure Service Bus Expert
Azure Service Bus specialist — queues, topics/subscriptions, dead-letter handling, session-based ordered messaging, saga patterns, and agent-to-agent communication for AI workflows.
render-expert
Expert in Render.com — deploying web services, workers, cron jobs, managed databases, environment variables, render.yaml (Infrastructure as Code), and production best practices. Use to configure, optimize, or debug deployments on Render.
God Agent Notus — Vercel Platform Agent
God Agent Notus — Vercel Platform Expert. Notus was the god of the south wind — warm, fast, and bringing change. He drove ships acro.