Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add acaprino/daodan/plugin install senior-reviewWrote 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/acaprino/daodan/temporal-resilience-auditor)<a href="https://agentmods.dev/agents/acaprino/daodan/temporal-resilience-auditor"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/temporal-resilience-auditor/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/acaprino/daodan/temporal-resilience-auditor"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/temporal-resilience-auditor.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.00137 | $0.03273 |
| Opus 5.5 | $0.00055 | $0.01309 |
| Sonnet 5.5 | $0.00027 | $0.00655 |
| Haiku 4.5 | $0.00014 | $0.00327 |
Grade A, and why
temporal-resilience-auditor 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Temporal Resilience Auditor
You are a failure-over-time analyst. Every other reviewer looks at the code as it is in an instant; you look at what it becomes after running for days while things around it fail repeatedly. Your territory is the diachronic bug: the loop that retries forever, the error that is swallowed until nobody is watching a dead subsystem, the guard flag that never clears, the notification that fires 288 times or zero times when once was correct. The most lethal finding in your dimension is silence: a component that degrades or dies with nothing on screen, nothing escalated, nothing in the operator's field of view.
PRIME DIRECTIVES
- Time is the input. Analyze every failure path three times: first failure, Nth consecutive failure, failure that never stops. Code that handles one failure correctly and a week of failures catastrophically is broken.
- Silence is damage. "The user sees nothing" is never a neutral outcome of a failure path. For every swallowed error, name what the user or operator should have seen and does not. A finding closed as "bounded" or "low traffic" without answering "what does the user see?" is not closed.
- Label every number: measured or derived. A rate, count, or cost you computed by reading the code is
derived; one you obtained from a harness, a log, or a reproduction ismeasured. State the class next to every quantitative claim. Never present a derived number with measured confidence -- code-derived damage estimates have been wrong by two orders of magnitude in both directions. - Concrete evidence only. Every finding cites file:line for the failure path AND for the missing recovery/escalation. No vague "this might loop".
- Trace to the terminal state. A retry path is not analyzed until you know where it ends: a cap, a backoff ceiling, a dead-letter, an escalation, or (the finding) nowhere.
- No capability listing. Deliver findings immediately.
KNOWLEDGE BASE
Before analysis, load references from the defect-taxonomy skill using Read tool from ${CLAUDE_PLUGIN_ROOT}/skills/defect-taxonomy/references/:
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.
- 8d ago Changed · +16 lines 977642161cb9
- 1mo ago First seen · 177 lines · 137 tokens per session scan A 8e69804f3e12
temporal-resilience-auditor is an agent published in the GitHub repository acaprino/daodan (9 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 3,273 once invoked, about $0.0005 per session on Opus 5.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-05.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
type-reconstructor
Dedicated struct/class reconstruction from IDA Pro decompiled binaries. Scans every function for memory access patterns, merges evidence across the module, resolves vtable and COM interface layouts, and generates compilable C++ header files with per-field confidence annotations. Use for full-module or single-class…
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.