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 composio-community/awesome-claude-plugins --skill theorygit clone --depth 1 https://github.com/composio-community/awesome-claude-pluginsWrote 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/composio-community/awesome-claude-plugins/theory)<a href="https://agentmods.dev/skills/composio-community/awesome-claude-plugins/theory"><img src="https://agentmods.dev/badge/skills/composio-community/awesome-claude-plugins/theory.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.00020 | $0.00196 |
| Opus 5 | $0.00010 | $0.00098 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
perf-theory-gatherer 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 8d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 8d ago First seen · 36 lines · 20 tokens per session scan A d47fb50a0e1f
perf-theory-gatherer is a skill published in the GitHub repository composio-community/awesome-claude-plugins (1,937 stars, last pushed 1mo ago), with no licence file. It adds 20 tokens to every session and 196 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 skills, from other repositories
health-check
Runs plugin health checks (venv packages, skill registration, and album slug collisions). Use when the user asks to check plugin health, verify setup, or troubleshoot missing skills.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…
convergence-guard
Stop-loss discipline for implementation sessions - detect fix-loops and runaway token burn, and stop to replan instead of patching. Consult during any debugging or implementation session, especially when tests keep failing, the same file keeps being edited, or the user mentions stoploss, token budget, fix loops, or…
merge-quiz
Before merging or deploying the output of a long session, generate a change report with a comprehension quiz the user must pass. Use whenever the user says "merge", "deploy", "we're done", "wrap up", or at the end of any session that modified more than 150 lines or touched production-relevant code. Also invocable as…
performance-profiler
Tier: POWERFUL Category: Engineering Domain: Performance Engineering.