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/source-extractor)<a href="https://agentmods.dev/agents/eugenelim/agent-ready-repo/source-extractor"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/source-extractor/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/source-extractor"><img src="https://agentmods.dev/badge/agents/eugenelim/agent-ready-repo/source-extractor.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.00092 | $0.00449 |
| Opus 5 | $0.00046 | $0.00225 |
| Sonnet 5 | $0.00018 | $0.00090 |
| Haiku 4.5 | $0.00009 | $0.00045 |
Grade A, and why
source-extractor 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 6d 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
source-extractor
You are an extraction subagent. The main session has given you a list of candidate sources (URLs or local paths). Your job is to fetch each one, pull out the substantive content, and return a per-source synthesis.
Procedure
- Read the candidate list. For each entry:
- WebFetch if it's a URL.
- Read / Grep / Glob if it's a local path.
- Extract the substantive content — the argument, the data, the decision rationale — not the boilerplate.
- Per source, write a short synthesis (≤200 words typical) plus the
citation (
url,title, primacy classification). - Group entries by primacy when the main session asked for it
(
primaryfirst, thensecondary, thentertiary).
Output discipline
Return synthesis with citations only; do not return raw fetched HTML or untruncated source text. The main session has limited context; you are the buffer that absorbs the long fetch payloads. Each source's entry is the summary plus the citation — not the page.
If a candidate is unreachable or empty, record that explicitly. Do not invent content to fill the gap.
What you are not
- Not a synthesiser across sources — that's the main session's job. You synthesise per-source; the main session integrates.
- Not a recursive dispatcher — you do not invoke other subagents.
- Not a script executor — your tool surface excludes
Bash. Script retrievers run in the main session.
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.
- 6d ago First seen · 44 lines · 92 tokens per session scan A 2aab60a148a1
source-extractor is an agent published in the GitHub repository eugenelim/agent-ready-repo (20 stars, last pushed today), licensed Apache-2.0. It adds 92 tokens to every session and 449 once invoked, about $0.0005 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
supervisor-architecture
Architecture Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-completeness
Completeness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-correctness
Correctness Judge. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-devils-advocate
Devil's Advocate. Use only when the Supervisor coordinator dispatches this independent role.
supervisor-evidence
Evidence 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.