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 commands/alex-ilgayev/mcpspy/issuegit clone --depth 1 https://github.com/alex-ilgayev/MCPSpyWrote 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/alex-ilgayev/mcpspy/issue)<a href="https://agentmods.dev/commands/alex-ilgayev/mcpspy/issue"><img src="https://agentmods.dev/badge/commands/alex-ilgayev/mcpspy/issue.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 | $0.00000 | $0.00026 |
| Opus 5 | $0.00000 | $0.00013 |
| Sonnet 5 | $0.00000 | $0.00005 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
issue 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 4d 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
Create an issue using the github-issue-creator skill. Here is the relevant info for the issue: #$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.
- 4d ago First seen · 4 lines · 0 tokens per session scan A 66a274750d32
issue is a command published in the GitHub repository alex-ilgayev/MCPSpy (517 stars, last pushed 7mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 26 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
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
release
Release a new version of rubyllm-agents to RubyGems and GitHub.
project
Manage projects inside a topic wiki. Projects are folders under output/projects/ that group related outputs (playbooks, images, code, data) with a goal captured in WHY.md.
manage-changes
Analyze and integrate PRD changes mid-development.
aod.status
View lifecycle stage summary and regenerate BACKLOG.md from GitHub Issues.
linear
Manage Linear tickets - create, update, comment, and follow workflow patterns.