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/known-issuesnpx skills add melodic-software/claude-code-plugins --skill known-issuesgit 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.00094 | $0.01641 |
| Opus 5 | $0.00047 | $0.00821 |
| Sonnet 5 | $0.00019 | $0.00328 |
| Haiku 4.5 | $0.00009 | $0.00164 |
Grade A, and why
known-issues 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 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.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
Claude Code version: !claude --version 2>/dev/null || echo "unknown"
Variables
Arguments: $ARGUMENTS
Purpose
Claude Code ships frequently. Features that worked last week may have new bugs today. This skill serves three purposes:
- Quick health check. Snapshot of registry health and model quality (no args needed)
- Proactive search. Find known bugs BEFORE you build on top of a feature
- Issue registry. Maintain single source of truth for the Claude product GitHub issues you track, record what they block, and create follow-up work items when bugs are fixed
Data Files
The issue registry (registry.json) persists in the registry directory. By default this is the
plugin's per-machine data directory (${CLAUDE_PLUGIN_DATA}, survives plugin updates). A consumer can
instead keep the registry inside their repository, git-tracked and team-shared, by setting the
registry_dir plugin option (personal user configuration).
Registry location. Apply to EVERY registry_manager.py invocation: the configured value is
${user_config.registry_dir}; the project root is ${CLAUDE_PROJECT_DIR}.
- If
${user_config.registry_dir}is a non-empty path → first require a contained project-relative value. Reject POSIX/rooted paths, Windows drive-qualified or drive-relative paths, UNC paths, any..segment with either separator, and any existing symlink path that resolves outside${CLAUDE_PROJECT_DIR}. If invalid, stop the registry action, report the configuration problem visibly, and direct/claude-ops:setup; do not join, normalize, create, or use the destination. If valid, pass--data-dir "${CLAUDE_PROJECT_DIR}/${user_config.registry_dir}". - If it is empty or still shows an unexpanded
${user_config.registry_dir}token (option unset) → OMIT--data-dir; the script falls back to${CLAUDE_PLUGIN_DATA}.
| File | Purpose | Who edits |
|---|---|---|
<registry-dir>/registry.json |
All tracked Claude product GitHub issues with status, category, affected files, and what's blocked | Skill (on search/scan --add/check-all), via scripts/registry_manager.py. See the registry-location rule above |
What ships with it
14 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.
- context/action-check-all.md 1.6 KB
- context/action-create.md 5.1 KB
- context/action-list.md 675 B
- context/action-quality.md 2.9 KB
- context/action-scan.md 1.8 KB
- context/action-search.md 2.1 KB
- context/action-status.md 1.7 KB
- context/issue-templates.md 1.0 KB
- context/output-templates.md 825 B
- context/registry-schema.md 544 B
- evals/evals.json 4.7 KB
- scripts/check-all.sh 2.5 KB runs code
- scripts/check-all.test.sh 5.2 KB runs code
- scripts/registry_manager.py 23 KB 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.
- 2d ago First seen · 160 lines · 94 tokens per session scan A b0a384d573e1
known-issues is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 1,641 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-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.