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 skills add mrclrchtr/supi --skill researchgit clone --depth 1 https://github.com/mrclrchtr/supiWrote 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/skills/mrclrchtr/supi/research)<a href="https://agentmods.dev/skills/mrclrchtr/supi/research"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/research/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/skills/mrclrchtr/supi/research"><img src="https://agentmods.dev/badge/skills/mrclrchtr/supi/research.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.00030 | $0.00274 |
| Opus 5.5 | $0.00012 | $0.00110 |
| Sonnet 5.5 | $0.00006 | $0.00055 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
research 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 16d 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.
This is a copy
100% identical to research — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Research
Do the research in the current foreground task. Use primary sources.
Process
- Define the exact question and the evidence needed to answer it.
- Collect evidence from the source that owns each fact:
- Use repository source and local documentation for repository facts.
- Use the installed Pi documentation and examples for Pi behavior or APIs.
- When available, use Context7 for focused third-party library documentation.
- Use
ghfor GitHub content. - When available, use
web_fetch_mdfor another public page. - When available, use
consulting_runonly for synthesis, design advice, or an independent second opinion. Do not treat its answer as a primary source.
- Follow important claims to the original specification, official documentation, source code, or first-party API.
- Answer the question with cited findings and unresolved gaps. Cite each material factual claim with a URL or repository path.
- Report the saved path and a short result summary.
When agent_run is available, use a read-only profile only for an independent repository investigation. Agent Runs are foreground work and do not replace primary web sources.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 16d ago Changed e8e9572e8664
- 29d ago Changed · -1 lines · -5 tokens per session 8e4ba32ed377
- 1mo ago Changed · +13 lines · -14 tokens per session a13cb8d4a920
- 1mo ago First seen · 13 lines · 49 tokens per session scan A af378829f015
research is a skill published in the GitHub repository mrclrchtr/supi (102 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 274 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to research, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
muse-delegate
Delegate a coding task to Muse Code (muse) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to Muse — phrasings like "have Muse do X", "delegate this to Muse", "run it through Muse", or "use Muse to implement/fix/refactor" — or wants…
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
review
Review a change for correctness, security, and missing tests.
pi-parity-review
Adversarially verify that a ported change is faithful to the original pi implementation (TS source + published npm build). Use after porting upstream pi changes, or standalone on any area of this repo ("is X faithful to pi?").
pi-go-review
Review ported Go code for idiomatic quality — that the port maximizes Go rather than transliterating TypeScript. Use after porting upstream pi changes, or standalone on any diff in this repo.
review-pr
Deeply review a GitHub pull request.