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 skills/richfrem/agent-plugins-skills/analyze-pluginnpx skills add richfrem/agent-plugins-skills --skill analyze-plugingit clone --depth 1 https://github.com/richfrem/agent-plugins-skillsWrote 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/richfrem/agent-plugins-skills/analyze-plugin)<a href="https://agentmods.dev/skills/richfrem/agent-plugins-skills/analyze-plugin"><img src="https://agentmods.dev/badge/skills/richfrem/agent-plugins-skills/analyze-plugin.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.00107 | $0.02189 |
| Opus 5 | $0.00053 | $0.01094 |
| Sonnet 5 | $0.00021 | $0.00438 |
| Haiku 4.5 | $0.00011 | $0.00219 |
Grade A, and why
analyze-plugin 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependencies
This skill requires Python 3.8+ and standard library only. No external packages needed.
To install this skill's dependencies:
pip-compile ./requirements.in
pip install -r ./requirements.txt
See ../../requirements.txt for the dependency lockfile (currently empty — standard library only).
Plugin & Skill Analyzer
Perform deep structural and content analysis on agent plugins and skills. Extract reusable patterns that feed the virtuous cycle of continuous improvement.
Two Analysis Modes
Single Plugin Mode
Deep-dive into one plugin. Use when you want to fully understand a plugin's architecture.
Comparative Mode
Analyze multiple plugins side-by-side. Use when looking for common patterns across a collection.
Analysis Framework
Execute these phases sequentially. Do not skip phases.
Phase 0: Quick Compliance Pre-Check
Before deep analysis, run a rapid compliance scan to surface blockers:
Manifest check:
# plugin.json must be in .claude-plugin/ (not root)
ls .claude-plugin/plugin.json && jq . .claude-plugin/plugin.json
namepresent and kebab-case (no spaces, no uppercase)?versionfollows semver (X.Y.Z) if present?- No unknown fields causing warnings?
Structure check:
- Component dirs (
commands/,agents/,skills/,hooks/) at plugin ROOT (not inside.claude-plugin/)? - All file names use kebab-case?
SKILL.md(notREADME.md) inside each skill directory?
Security scan:
# Hardcoded credentials
grep -rn "password\|api_key\|secret" --include="*.md" --include="*.json" --include="*.sh" .
# Hardcoded paths (should use ${CLAUDE_PLUGIN_ROOT})
grep -rn "/Users/\|/home/" --include="*.json" --include="*.sh" .
Report Phase 0 findings before proceeding. If CRITICAL issues found (invalid JSON, hardcoded credentials, missing required fields), flag them prominently in the final report.
Phase 1: Inventory
Run the deterministic inventory script first:
python "scripts/inventory_plugin.py" --path <plugin-dir> --format json
What ships with it
23 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.
- acceptance-criteria.md 1.4 KB
- assets/resources/analyze-plugin-flow.mmd 51 B
- evals/evals.json 810 B
- evals/results.tsv 301 B
- fallback-tree.md 1.5 KB
- references/acceptance-criteria.md 42 B
- references/ADRs/001_cross_plugin_script_dependencies.md 62 B
- references/ADRs/002_multi_skill_script_centralization.md 63 B
- references/ADRs/003_plugin_skill_resource_sharing_via_mirrored_folder_structure_and_file_level_symlinks.md 113 B
- references/ADRs/004_self_contained_plugins_no_cross_plugin_dependencies.md 81 B
- references/ADRs/005_plugin_separation_of_concerns_and_loose_coupling.md 78 B
- references/ADRs/006_python_native_plugin_bootstrap_installer.md 70 B
- references/analysis-framework.md 41 B
- references/analysis-questions-by-type.md 49 B
- references/diagrams/analyze-plugin-flow.mmd 55 B
- references/fallback-tree.md 36 B
- references/inventory_plugin.py 39 B runs code
- references/maturity-model.md 37 B
- references/output-templates.md 39 B
- references/pattern-catalog.md 38 B
- references/security-checks.md 38 B
- requirements.txt 22 B
- scripts/inventory_plugin.py 36 B runs code
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.
- today First seen · 220 lines · 107 tokens per session scan A ff0504013548
analyze-plugin is a skill published in the GitHub repository richfrem/agent-plugins-skills (6 stars, last pushed today), licensed MIT. It adds 107 tokens to every session and 2,189 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
kapso-whatsapp
How to interact with Kapso WhatsApp from the swarm — read inbound webhook payloads (text AND media), fetch message history, send free-form messages within the 24h session window (and template messages outside it), mark-as-read, show the typing indicator, send reactions, download media, verify webhook signatures, and…
composio
Use Composio from Agent Swarm through the agent-swarm x composio CLI route, the swarmx MCP tool, or a registered ctx.api.composio script connection. Trigger when a task needs connected third-party app tools such as Gmail, Google Calendar, Google Docs, Google Drive, GitHub, Slack, Notion, or HubSpot through Tool Router…
attio-interaction
Generic Attio CRM REST API v2 recipes for querying records, upserting companies/people/deals, writing notes/tasks/comments, managing lists, and handling webhooks.
scheduled-task-resilience
Guardrails for polling, scheduled jobs, and long-running external operations. Use whenever a task waits on CI, builds, deploys, browser jobs, or another asynchronous API so work survives heartbeat checks without duplicate delivery.
swarm-scripts
Bulk, repeat, fan-out, or data-heavy work: write and run swarm scripts (inline script-run, named script-upsert, durable launch-script-run). Covers the script-vs-tool rubric, the authoring contract (args first, ctx second), the seed catalog, connections and secrets, dbquery, and exposing a script as an API.
user-management
How to manage the user registry — creating users for new Slack/GitHub/GitLab/Linear identities, managing aliases, resolving users across platforms. Use when a new human interacts with the swarm or when user identity needs updating.