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 melodic-software/claude-code-plugins --skill known-issuesgit clone --depth 1 https://github.com/melodic-software/claude-code-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/melodic-software/claude-code-plugins/known-issues)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/known-issues"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/known-issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/known-issues"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/known-issues.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.01894 |
| Opus 5.5 | $0.00034 | $0.00758 |
| Sonnet 5.5 | $0.00017 | $0.00379 |
| Haiku 4.5 | $0.00009 | $0.00189 |
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 3d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments. <status|search|check-all|scan|list|quality|create> [args]. Full form: [args]. Actions: status (default), search, check-all, scan, list, quality, create. e.g., 'search Stop hook', 'check-all', 'create bug "title"'
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/harness-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) → pass--data-dir "${CLAUDE_PLUGIN_DATA}". The Bash tool's environment does not carry this plugin'sCLAUDE_PLUGIN_DATA, and another plugin's SessionStart hook can export its own data directory under that name, so the script uses an inherited value only when it names harness-ops (Basis and recheck trigger: Spoke paths).
What ships with it
15 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 2.6 KB
- context/action-create.md 5.1 KB
- context/action-list.md 676 B
- context/action-quality.md 3.4 KB
- context/action-scan.md 1.8 KB
- context/action-search.md 2.8 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 543 B
- evals/evals.json 4.7 KB
- scripts/check-all.sh 6.6 KB runs code
- scripts/check-all.test.sh 15 KB runs code
- scripts/registry_manager.py 25 KB runs code
- scripts/test_registry_manager.py 5.3 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.
- 3d ago Changed · -4 lines · -7 tokens per session cc3e52a82f92
- 10d ago Changed 0123ae42eb36
- 14d ago Changed · +6 lines · -1 tokens per session f317bffa0f7e
- 14d ago Changed 45e61922a142
- 16d ago Changed · +10 lines 3102f894d012
- 18d ago Changed · +2 lines 46e2da008e82
- 1mo 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 (26 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,894 once invoked, about $0.0003 per session on Opus 5.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
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.
benchmark-before-optimize
For performance work: measure before changing, profile to find bottlenecks, compare before and after.
validate-before-process
For input validation: check format and constraints before processing, fail fast with clear errors, defensive parsing.
display-grid-state
For 2D debugging: visualize grid/board state, show puzzle progress, make algorithm behavior visible.
handle-edge-cases
For boundary conditions: empty collections, zero values, recursive base cases, null checks, prevent crashes at edges.
claim-check
Claim checker that audits a coding agent's statements that tests pass or a build is clean against its own session transcripts: whether a matching run happened before the claim, whether it passed, and whether code changed after it. Use when the user asks whether the agent really ran the tests, how often it said tests…