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/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/commands/marazii/research-co-pilot/analyze)<a href="https://agentmods.dev/commands/marazii/research-co-pilot/analyze"><img src="https://agentmods.dev/badge/commands/marazii/research-co-pilot/analyze.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.00019 | $0.00224 |
| Opus 5 | $0.00010 | $0.00112 |
| Sonnet 5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 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
Invoke the data-analysis skill from the research-co-pilot plugin and execute its full workflow.
The skill file is at skills/data-analysis/SKILL.md relative to this plugin. Read it and follow it precisely — including:
- Phase 1: Frame the question (descriptive / inferential / predictive / causal).
- Phase 2-3: Load, inspect, clean — show output to user before transforming.
- Phase 4: EDA before modeling.
- Phase 5-6: Baseline model first; check assumptions; report with effect sizes and CIs.
- Phase 7-8: Visualize and produce
analysis_<topic>.md+ reproducible script.
For heavy computation, delegate to the data-cruncher subagent.
User input: $ARGUMENTS
If no dataset path or question was given, ask where the data lives and what question to answer.
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 · 21 lines · 19 tokens per session scan A 3fae332d1259
analyze is a command published in the GitHub repository Marazii/research-co-pilot (13 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 224 once invoked, about $0.0001 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 commands, from other repositories
wp-cleanup
Find and clean up unused PHP code, Composer dependencies, imports, and dead code in WordPress projects.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.
a
Intercept Mode - Auto-improve and execute immediately.
speckit.tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
prep
Prepare a pre-meeting briefing by reviewing all memory files and surfacing items that need discussion.
checklist
Generate a custom checklist for the current feature based on user requirements.