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/melodic-software/claude-code-plugins/inventorynpx skills add melodic-software/claude-code-plugins --skill inventorygit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00214 | $0.03105 |
| Opus 5 | $0.00107 | $0.01553 |
| Sonnet 5 | $0.00043 | $0.00621 |
| Haiku 4.5 | $0.00021 | $0.00311 |
Grade A, and why
inventory scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Any claim about what Claude Code itself ships must come from the raw markdown endpoint. `curl -sSL` How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Answers one question completely: what can this machine actually invoke, and where did each thing come from?
That question has no single documented answer. Claude Code's own documentation does not publish a
list of its built-in slash commands. docs/en/slash-commands now serves the skills page, because
commands were merged into skills, so the only complete source for the built-in surface is the
shipped executable. Plugin components, by contrast, are on disk and enumerable directly. This skill
reads both and keeps them clearly separated, because they are evidence of different quality.
The report is an inventory, not a judgement. Nothing here says a component is stale, misconfigured, or wrong; the neighbours below own those verdicts.
Scope boundary
| Question | Owner |
|---|---|
| What can I invoke, and where did it come from? | this skill |
| Is my install directory healthy. What is stale, what does the product manage? | /claude-ops:audit-install-state |
| Is the plugin fleet current, and at what scope? | /claude-ops:plugins audit |
| Are settings, hooks, permissions, and MCP config correct? | /claude-config:audit |
| Which permission scopes hold which rules? | /claude-config:audit-permission-state |
The distinction that matters most: audit-install-state inventories files on disk, this skill
inventories capabilities that resolve. A plugin can be present on disk and contribute nothing
because it is disabled, and a built-in command can be fully live while existing nowhere on disk.
Run it
python3 "${CLAUDE_PLUGIN_ROOT}/skills/inventory/scripts/inventory.py" --out ./claude-inventory.json
Python 3.11+ is the only requirement. No strings, no jq, no PowerShell, no third-party
packages. The run takes a few seconds, dominated by reading the executable once.
Useful flags: --binary <path> (else auto-detected) · --config-dir <path> (else
$CLAUDE_CONFIG_DIR, else ~/.claude) · --binary-only / --disk-only to skip a source.
What ships with it
4 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.
- 2d ago First seen · 221 lines · 214 tokens per session scan A d398c814b0e8
inventory is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 214 tokens to every session and 3,105 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.