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 extract-ssotgit 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/extract-ssot)<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/extract-ssot"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/extract-ssot/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/extract-ssot"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/extract-ssot.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00099 | $0.05848 |
| Opus 5.5 | $0.00040 | $0.02339 |
| Sonnet 5.5 | $0.00020 | $0.01170 |
| Haiku 4.5 | $0.00010 | $0.00585 |
Grade A, and why
extract-ssot 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 12d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Arguments. [identify|verify|plan|execute|batch|unwind] [<cluster>] [--fix] [--dry-run] [--yes]. Full form: [identify|verify|plan|execute|batch|unwind] [] [--min-instances=] [--buckets=] [--fix] [--dry-run] [--yes] [--inline] [--parallel-waves] [--commit-mode=<per-wave|single|none>]
Extract SSOT
Why this skill exists
Codifies the markdown-SSOT-extraction pattern as a repeatable workflow. Each invocation targets ONE cluster of repeated markdown content and resolves it to a single named source of truth, consolidating into an existing SSOT home when one already owns the concept, otherwise creating a new artifact (e.g. a rule file or a new skill), plus migration of all call sites to cite by exact heading.
The principle is the coding Rule of Three / DRY, applied to markdown text. If the same unit of prose appears 3+ times, changes together, and has an identity that can be named, collapse to one definition and reference by name. Below 3 instances, minting a new SSOT artifact is premature abstraction, the dominant failure mode, and the skill refuses it.
Refusing to create is not refusing to report. A lone consumer that recaps an SSOT it should be citing, and a pair of files asserting the same contract with no declared owner, are real defects that drift. Both are rostered in their own multiplicity bucket and remedied in place, with no new artifact.
Typical markdown extraction shapes the workflow handles:
- A vocabulary of CLI/API verbs that many prompts, skills, and rules invoke inline. Collapsed into one rule file with stable headings the call sites cite
- A constraint or guardrail repeated across multiple skills (e.g. "always run X before Y"). Promoted to a single always-loaded rule
- A workflow primitive appearing across several skills. Extracted to a shared primitive doc that skills cite by name
Extraction is dangerous: on SkillsBench, 16 of 84 tasks come out worse with a curated skill than without one, about 19 percent. The dated record for that figure is in context/decision-framework.md. This skill encodes the guardrails (Rule of Three, categorical-shape test, the size bound and one-level depth rule /playbooks:skill-authoring ## Body and ## Reference files record, Metz unwind procedure) so each invocation is reversible and reviewable.
What ships with it
12 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.
- actions/batch.md 14 KB
- actions/identify.md 28 KB
- actions/verify.md 19 KB
- context/anti-patterns.md 21 KB
- context/citation-form.md 6.5 KB
- context/decision-framework.md 25 KB
- context/execution-checklist.md 11 KB
- context/lessons.md 24 KB
- context/orchestrated-mode.md 10 KB
- evals/evals.json 11 KB
- scripts/emit-verify-facts.sh 2.5 KB runs code
- scripts/emit-verify-facts.test.sh 3.7 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.
- 12d ago Changed 45269670cc7d
- 20d ago Changed · +2 lines b69aa4bcd413
- 21d ago Changed · +4 lines · -26 tokens per session 5de3890b7e91
- 27d ago Changed 6942861916c7
- 1mo ago Changed · -5 tokens per session 5633a1c0717e
- 1mo ago Changed 4a43f68114db
- 1mo ago Changed · +1 lines 94885e757e66
- 1mo ago First seen · 244 lines · 130 tokens per session scan A 80ceca73fa50
extract-ssot is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 99 tokens to every session and 5,848 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
parallel-orchestrator
Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…
parallel-worker
Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.
optimize-local-search
For NP-hard optimization: TSP, scheduling, assignment problems. Uses greedy construction + local improvement (2-opt, hill climbing).
solve-constraint-puzzle
For constraint satisfaction: Sudoku, scheduling, N-queens, logic puzzles, SAT-like problems, assignment problems. Uses propagate-then-search pattern.
test-with-examples
For example-driven development: test cases as specifications, input/output pairs, documentation through examples.
validate-before-process
For input validation: check format and constraints before processing, fail fast with clear errors, defensive parsing.