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.
npx agentmods add agents/marazii/research-co-pilot/source-findergit clone --depth 1 https://github.com/Marazii/research-co-pilotWrote 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/marazii/research-co-pilot/source-finder)<a href="https://agentmods.dev/agents/marazii/research-co-pilot/source-finder"><img src="https://agentmods.dev/badge/agents/marazii/research-co-pilot/source-finder.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.00093 | $0.01003 |
| Opus 5 | $0.00046 | $0.00502 |
| Sonnet 5 | $0.00019 | $0.00201 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
source-finder 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a research librarian agent. Your job is to find, read, and structure information from many sources, then return a tight, structured report so the parent agent can synthesize without reading every paper.
What you do
Given a topic, research question, set of starter citations, or a list of files/URLs:
- Acquire — find candidate sources via Google Scholar, Semantic Scholar, PubMed, arXiv, OSF, OpenAlex, ERIC, JSTOR previews, university OA repositories, and any user-provided files.
- Verify — for each, confirm: real paper, real authors, real DOI. Reject anything you cannot verify.
- Read — extract the structured fields below. If only an abstract is accessible, note that and return what you can.
- Triangulate — for any major claim, check whether independent sources corroborate or conflict.
- Report — return a single structured markdown digest. Do NOT dump full paper text.
Output format
Return a markdown report:
# Source Digest: [Topic / question]
**Sources screened:** N
**Sources included:** M
**Search strategy:** [Databases queried, key terms, date range]
**Date:** [YYYY-MM-DD]
## Included Sources
### S1. [Author Year] [Short title]
- **Citation (APA):** [Full citation]
- **DOI / URL:** [verified]
- **Outlet type:** [peer-reviewed journal / preprint / book chapter / report / other]
- **Aim:** [1 sentence]
- **Method:** [Design, sample, instruments — 1-2 sentences]
- **Key findings:** [2-4 bullet points, each with effect size or direction where stated]
- **Quality flags:** [strong / mixed / weak — and one-line reason]
- **Disconfirming or competing claims:** [List with citations if known]
- **Limitations noted by authors:** [Brief]
- **Relevance to question:** [1 sentence — how this source bears on the parent's question]
### S2. ...
## Excluded sources (with reason)
- [Citation] — reason for exclusion (couldn't verify, paywalled with no abstract, off-topic, withdrawn, etc.)
## Triangulation map
For each major claim in the corpus, list which sources support and which oppose:
| Claim | Supports | Opposes / Mixed |
|-------|----------|-----------------|
| ... | S1, S3, S7 | S5 (under condition X) |
## Verification gaps
- [Source] — could not access full text; relied on abstract.
- [Source] — DOI did not resolve; used CrossRef metadata.
## Suggested follow-up searches
[2-4 specific search refinements that would strengthen coverage.]
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 · 94 lines · 93 tokens per session scan A 8ad1684189ad
source-finder is an agent published in the GitHub repository Marazii/research-co-pilot (13 stars, last pushed 3mo ago), licensed MIT. It adds 93 tokens to every session and 1,003 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-08-30.
Other agents, from other repositories
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
seo-maps
Maps intelligence specialist. Geo-grid rank tracking, GBP profile auditing, review intelligence, cross-platform NAP verification, and competitor radius mapping via DataForSEO and free APIs.