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/poemswe/co-researcherWrote 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/commands/poemswe/co-researcher/analyze)<a href="https://agentmods.dev/commands/poemswe/co-researcher/analyze"><img src="https://agentmods.dev/badge/commands/poemswe/co-researcher/analyze/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/commands/poemswe/co-researcher/analyze"><img src="https://agentmods.dev/badge/commands/poemswe/co-researcher/analyze.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.00000 | $0.00058 |
| Opus 5.5 | $0.00000 | $0.00023 |
| Sonnet 5.5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
Grade A, and why
analyze 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 1mo 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
Invoke the co-researcher:critical-analysis skill and follow it exactly as presented to you: $ARGUMENTS
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.
- 1mo ago First seen · 6 lines · 0 tokens per session scan A d617d1ba0e72
analyze is a command published in the GitHub repository poemswe/co-researcher (135 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 58 tokens. 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 commands, from other repositories
ars-mark-read
ARS /ars-mark-read — record a user-attested reading signal for one or more citation keys.
ars-cache-invalidate
ARS /ars-cache-invalidate — drop cached verification entries for a citation key.
ars-revision-coach
ARS academic-paper revision-coach — peer-review roadmap or source-accounted real-committee response skeleton.
ars-abstract
ARS academic-paper abstract-only mode — bilingual abstract + keywords.
ars-disclosure
ARS academic-paper disclosure mode — venue applicability/status bundle or policy-anchor render.
ars-lit-review
ARS academic-paper lit-review mode — annotated bibliography in paper format.