timps_incident_responder

timps_incident_responder is an agent for Claude Code from Sandeeprdy1729/timps-swarm. It costs 61 tokens per session (494 once invoked), scanned A, original, MIT.

An incident-analysis agent that combines Docker and application logs into a timeline and triage report. It is designed to be called by another agent.

In plain words
What is it for?
Use it to correlate logs, build an incident timeline, and prepare an initial triage report.
Why use it?
It reduces the manual work of searching separate log sources and reconstructing what happened during a production outage.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents.

Good fit Use it to correlate logs, build an incident timeline, and prepare an initial triage report.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/sandeeprdy1729/timps-swarm/timps-incident_responder
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Sandeeprdy1729/timps-swarm

Made for: Claude Code.

Wrote 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.

agentmods badge for timps_incident_responder

README.md
[![agentmods](https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-incident_responder/github.svg)](https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-incident_responder)
Your own site
<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-incident_responder"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-incident_responder/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.

agentmods 80×15 button for timps_incident_responder

Your own site · 80×15
<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-incident_responder"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-incident_responder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 494 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.00494
Opus 5 $0.00030 $0.00247
Sonnet 5 $0.00012 $0.00099
Haiku 4.5 $0.00006 $0.00049

Measured 7d ago against content hash c5ee80e475e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

timps_incident_responder 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.

.claude/agents/timps-incident_responder.md · 45 lines

What it actually says

incident responder

You are the incident responder sub-agent from the TIMPS Swarm (category: expert).

Your job

Multi-source log correlation for production incidents. Gathers Docker + app logs, builds a timeline, and generates a triage report.

How to respond

  1. Always call the MCP tool timps_incident_responder exactly once via the mcp__timps-swarm__timps_incident_responder tool handle.
  2. Pass the user's request verbatim in the input — do not summarise, do not pre-empt.
  3. Wait for the tool's text response and return it to the parent agent. The tool output is the result.
  4. Do not try to answer from your own knowledge — this sub-agent exists to route to the TIMPS specialist.
  5. 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_incident_responder 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.

Changes

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.

  1. 7d ago First seen · 45 lines · 61 tokens per session scan A c5ee80e475e1

Subscribe to this mod's changes

timps_incident_responder is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 8d ago), licensed MIT. It adds 61 tokens to every session and 494 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.

Related

Other agents, from other repositories

cicd-automation-devops-troubleshooter

Expert DevOps troubleshooter specializing in rapid incident response, advanced debugging, and modern observability. Masters log analysis, distributed tracing, Kubernetes debugging, performance optimization, and root cause analysis. Handles production outages, system reliability, and preventive monitoring. Use…

wshobson/agents · 74 tokens

megalinter-runner

Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.

ulises-jeremias/agent-toolkit · 65 tokens

stata-debugger

Stata error diagnosis and debugging agent. Invoke when a user reports a Stata error, unexpected output, rc code, or do-file that is not working as expected.

tmonk/mcp-stata · 38 tokens

God Agent Asclepius — Debugging & Diagnostics Agent

God Agent Asclepius — Debugging & Diagnostics. God of medicine and healing, who could diagnose any affliction and cure it — so skilled he.

Holley-Studio/thesmos-governance · 45 tokens

God Agent Momus — Challenger & Clarity Enforcer

God Agent Momus — Challenge & Clarity Enforcement. God of mockery, blame, and criticism — the one god on Olympus who challenged everything, i.

Holley-Studio/thesmos-governance · 44 tokens

God Agent Proteus — Drift & Alignment Monitor

God Agent Proteus — Drift Detection & Alignment Monitoring. The ancient sea god who knows all things and constantly changes shape. Only those who hold.

Holley-Studio/thesmos-governance · 39 tokens