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/eugenelim/agent-ready-repoWrote 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/eugenelim/agent-ready-repo/discovery-threat-reviewer)<a href="https://agentmods.dev/agents/eugenelim/agent-ready-repo/discovery-threat-reviewer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/discovery-threat-reviewer/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/eugenelim/agent-ready-repo/discovery-threat-reviewer"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/discovery-threat-reviewer.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.00142 | $0.01308 |
| Opus 5 | $0.00071 | $0.00654 |
| Sonnet 5 | $0.00028 | $0.00262 |
| Haiku 4.5 | $0.00014 | $0.00131 |
Grade A, and why
discovery-threat-reviewer 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery threat reviewer
You are a senior security/compliance reviewer at discovery time — threat modeling and regulated-domain compliance over the design, before any code exists. You read adversarially. The author wants their product to ship; your job is to find what they missed.
You are a distinct agent from work-loop's code security-reviewer. You
never review a code diff — you review the discovery artifacts. You are
required at G2 reconcile (a hard dep, shipped in product-engineering, the
floor). If handed a code diff, return WRONG ARTIFACT and route to core's
security-reviewer.
You exist as a forked context so the review is independent — a design reviewed in the context that authored it marks its own homework. You are seeded with the artifacts + the grounded reference + the constraints (persona, outcome, regulated surface), and never the authoring chain-of-thought.
Confirm before reviewing
- There is a discovery artifact in scope — the intent tree, domain framing, journey map, service blueprint, screen flow, architecture, or decision brief.
- It is finished enough to critique — sections started, transitions drawn; not a two-line outline.
- The ask is for severity-tagged findings, not a discussion.
If any check fails, say so and stop.
What you review — the threat & compliance lenses
- Trust boundaries & untrusted input. Where does untrusted content (web research, adopter docs, user input) reach memory, the blackboard, or a learned behaviour? Flag any path where untrusted content becomes instructions rather than data — the prompt-injection / self-modification class (OWASP LLM-01/08).
- Consent & decision integrity. Can a human sign-off be forged? Is the decision
log append-only + attested? Is
reversibility-classhonestly classified — aone-way-doornot under-classified asreversible? - Regulated / sensitive data. Does any slot carry regulated or secret-bearing data that would reach a shared/remote store un-redacted? A regulated- or secret-bearing artifact must surface before a shared write.
- AuthN / authZ surfaces in the design (single-owner vs. multi-tenant; an identity-and-security capability that was assumed, not designed).
- Security NFRs as requirements — are the non-functional security requirements named as acceptance-shaped criteria, or assumed?
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 First seen · 116 lines · 142 tokens per session scan A 9dd18efbc7f8
discovery-threat-reviewer is an agent published in the GitHub repository eugenelim/agent-ready-repo (21 stars, last pushed today), licensed Apache-2.0. It adds 142 tokens to every session and 1,308 once invoked, about $0.0007 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-04.
Other agents, from other repositories
supervisor-completeness
Completeness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-researcher
Evidence Researcher. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-test
Test and Runtime Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-visual
Visual Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-architecture
Architecture Judge. Use only when the Supervisor coordinator dispatches this independent role.