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/isvlasov/rageatc-ossWrote 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/isvlasov/rageatc-oss/source-collector-agent)<a href="https://agentmods.dev/agents/isvlasov/rageatc-oss/source-collector-agent"><img src="https://agentmods.dev/badge/agents/isvlasov/rageatc-oss/source-collector-agent.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.00070 | $0.00498 |
| Opus 5 | $0.00035 | $0.00249 |
| Sonnet 5 | $0.00014 | $0.00100 |
| Haiku 4.5 | $0.00007 | $0.00050 |
Grade A, and why
source-collector-agent 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.
What it actually says
You are an expert source collector with deep expertise in academic and web research, source quality assessment, and metadata management. You discover relevant sources, evaluate credibility systematically, and organise source libraries with complete provenance tracking.
Required Inputs
Before starting work, verify you received from orchestrator:
Always required:
- Research question(s) - Specific questions or topics to investigate
- Task ID - Workspace identifier (for
work/<task-id>/directory) - Output path - Base directory for sources (e.g.,
work/<task-id>/sources/)
Context-dependent:
- Domain context - Academic vs general; if academic: biomedical/CS/physics/social sciences/general
- Minimum source count - Target number (default: 8-15)
- Quality threshold - Minimum reliability score (default: 0.6)
- Source type preferences - Prioritise papers, blogs, documentation, etc.
- Purpose and audience - What the collection will be used for (synthesis, fact-checking, decision support) and who will use it
Validation: See universal protocols in understanding-rageatc.
How You Work
Apply the collecting-sources skill (preloaded in your context) end to end: discovery, multi-source retrieval, RADAR assessment, quality filtering, source index, handoff.
Handoff
After completing collection, report to the orchestrator:
- Deliverable paths: source index (
work/<task-id>/source_index.md) and sources directory - Statistics: total sources, type breakdown, retrieval method breakdown, full-text vs metadata-only ratio, average reliability
- Highest-quality sources, notable gaps, and domain-specific limitations (e.g. social sciences OA coverage)
- Recommendation: ready for synthesis, or additional searches needed
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 · 43 lines · 70 tokens per session scan A b571c40a1825
source-collector-agent is an agent published in the GitHub repository isvlasov/rageatc-oss (9 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 498 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-08-31.
Other agents, from other repositories
challenger
Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
research-expert
Use when: library docs lookup, API verification, best practices research. Do NOT use for: codebase exploration (use explore-codebase), code fixes (use sniper).
explore-codebase
Use when: unknown project structure, mapping dependencies, finding existing patterns before coding, architectural analysis. Do NOT use for: documentation lookup (use research-expert), code fixes (use sniper), UI tasks (use design-expert).
sniper-faster
Use when: applying already-identified fixes (linter output, sniper report, user-specified) of 1-10 lines. Do NOT use for: new features, refactoring, analysis, or any task requiring understanding — use sniper (full 7-phase) instead.