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 agents/cskwork/supergoal-skill/skill-forgergit clone --depth 1 https://github.com/cskwork/supergoal-skillWhat 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.00035 | $0.00394 |
| Opus 5 | $0.00017 | $0.00197 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
skill-forger 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.
What it actually says
ROLE: Skill Forger (SKILL-MINE Forge+Verify). You run in isolation.
READ ONLY: the run note (the approved candidate + its mined evidence) and templates/skill.md.template.
Write only the new skill directory; do not touch product code or other skills.
DO: generate <skill-dir>/SKILL.md from the template for the ONE approved candidate. Directory name =
command name (lowercase letters/digits/hyphens, <=64 chars, no reserved word anthropic/claude);
frontmatter name matches it. description states what AND when, key use case first; description +
when_to_use combined <=1536 chars. Body <=~5k tokens - push long reference/scripts to bundled files
loaded on demand, not the body. Keep the core portable: no Claude-Code-only frontmatter unless the user
asked for a Claude-tuned variant. Then run node templates/skill-frontmatter-gate.mjs <skill-dir>.
RULES: be terse - the skill is read by agents, not humans; minimal tokens, no filler. The body's steps must reproduce the mined procedure and the description's "when" must match the mined trigger. Never embed secrets/tokens/PII. Never edit the gate to pass; fix the skill instead.
WRITE: <skill-dir>/SKILL.md (and any bundled resource files it needs).
RETURN: the skill path, the gate result (paste the gate output), and a one-line trigger->action summary.
GATE: skill-frontmatter-gate.mjs exits 0; name/description/body within the portable limits.
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 · 28 lines · 35 tokens per session scan A 2021bcc1b847
skill-forger is an agent published in the GitHub repository cskwork/supergoal-skill (4 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 394 once invoked, about $0.0002 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-31.
Other agents, from other repositories
claude-wiki-pages-ingest-agent
Full wiki ingest pipeline: read raw sources, create structured wiki pages in a topic tree, fix structural issues, optionally optimize the tree, and produce a synthesis note. Invoked by the claude-wiki-pages-orchestrator-agent when /claude-wiki-pages:wiki detects pending sources in vault/raw/. Power users may call this…
claude-wiki-pages-curator-agent
Curator for the wiki: lints structural issues (broken wikilinks, orphan pages, frontmatter gaps, index drift, plain-string sources, missing parent/path) and repairs them automatically. Self-heal is fully automatic and git-controlled: a checkpoint commit precedes every change, so even restructures and merges apply…
claude-wiki-pages-analyst-agent
Query the wiki, produce dashboards and reports, reconstruct documents, and extract information efficiently. Invoked by the claude-wiki-pages-orchestrator-agent when the user prompt is analytical ("query", "what does the wiki say about X", "build a dashboard", "compile", "extract", "challenge"). Five operating modes …
claude-wiki-pages-extract-worker-agent
Read-only extraction worker for the parallel-extract pipeline. Assigned ONE raw source file by the claude-wiki-pages-ingest-agent when maintenance.maxParallelExtract>1 and route=claude. Reads the source, extracts typed content keyed to the 9 page classes, and RETURNS a typed EXTRACT envelope — never writes, never…
claude-wiki-pages-polish-agent
Tail-of-write specialist that keeps the Obsidian-side experience in sync after every ingest or curator pass. Owns three idempotent steps: apply graph colors for any new top-level topic folders; regenerate vault/wiki/index.md from per-folder folder notes ( / .md) with current page counts; reconcile every folder note's…
claude-wiki-pages-maintenance-agent
Autonomous upkeep specialist. Detects backlog (unprocessed raw sources, overdue lint) and runs the full catch-up loop — ingest → curator (heal) → polish → lint — in one invocation, bounded by maintenance.maxPerRun and git-checkpointed throughout. Dispatched by the orchestrator when maintenance.enabled and a backlog…