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-code_archaeology)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps-swarm/timps-code_archaeology"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps-swarm/timps-code_archaeology.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.00053 | $0.00478 |
| Opus 5 | $0.00026 | $0.00239 |
| Sonnet 5 | $0.00011 | $0.00096 |
| Haiku 4.5 | $0.00005 | $0.00048 |
Grade A, and why
timps_code_archaeology 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
77% identical to timps_ab_testing_agent — 18 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
code archaeology
You are the code archaeology sub-agent from the TIMPS Swarm (category: expert).
Your job
Analyse git history to build an AST import graph, risk map, and tribal knowledge document.
How to respond
- Always call the MCP tool
timps_code_archaeologyexactly once via themcp__timps-swarm__timps_code_archaeologytool 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_code_archaeology 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 · 53 tokens per session scan A 0457ae97c592
timps_code_archaeology is an agent published in the GitHub repository Sandeeprdy1729/timps-swarm (1 stars, last pushed 5d ago), licensed MIT. It adds 53 tokens to every session and 478 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to timps_ab_testing_agent, differing in 18 lines, and is treated as a copy.
Other agents, from other repositories
God Agent Kronos — GitHub Repository Agent
God Agent Kronos — GitHub Repository & Release Management. Titan god of time and ages. Kronos ordered the cosmos by controlling what happens when — b.
reviewer
Review artifacts against intent and contracts, recommend, etc. Full subagent.
kicad-design-review-agent
Performs a thorough hardware design review of a KiCAD project. Triggers: full design review, audit everything, is my board ready for fab, comprehensive check, pre-fab review.
commit-pusher
Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.
tech-lead-consolidator
Tech lead AFTER the code is written. Convergence point for advisory reports, arbitrates conflicts, issues the final merge verdict, owns rollback plan and deploy considerations.
pn-skeptic
Specialist: fast automated plan challenge — questions the approach, lists alternatives and tradeoffs, outputs proceed/revise verdict. Use for a single-pass review. For interactive Socratic dialogue, use pn-grill instead.