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/agricidaniel/skill-forge/skill-forge-evolvenpx skills add AgriciDaniel/skill-forge --skill skill-forge-evolvegit clone --depth 1 https://github.com/AgriciDaniel/skill-forgeWhat 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.00081 | $0.01650 |
| Opus 5 | $0.00041 | $0.00825 |
| Sonnet 5 | $0.00016 | $0.00330 |
| Haiku 4.5 | $0.00008 | $0.00165 |
Grade A, and why
skill-forge-evolve 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Evolution & Improvement
Process
Step 1: Diagnose the Issue
Ask the user or analyze logs to identify the problem category:
Category A: Triggering Issues
- Under-triggering: Skill doesn't activate when it should
- Over-triggering: Skill activates when it shouldn't
- Mis-triggering: Wrong sub-skill activates
Category B: Execution Issues
- Incomplete workflows: Skill stops before finishing
- Incorrect output: Results don't match expectations
- Missing error handling: Failures not handled gracefully
- Performance: Too slow or too many token used
Category C: Architecture Issues
- Missing capability: New use case not covered
- Scale issues: Skill too large, needs decomposition
- Cross-reference problems: Links to non-existent files
Category D: Quality Issues
- Inconsistent results: Different outputs for same input
- Vague instructions: Claude interprets differently each time
- Missing examples: No concrete guidance
Step 2: Apply Fix by Category
Fix: Under-Triggering
- Read current description
- Identify missing trigger phrases
- Add domain keywords and paraphrases
- Add file type mentions if relevant
- Test with 5 queries that should now trigger
Common causes:
- Description too generic
- Missing common paraphrases
- Technical jargon without lay terms
Fix template:
# Before (under-triggers)
description: Analyzes code quality
# After (specific triggers)
description: >
Static code analysis and quality assessment. Checks code style,
complexity, security vulnerabilities, and test coverage. Use when
user says "code review", "code quality", "lint", "static analysis",
"code smell", "code audit", or "check my code".
Fix: Over-Triggering
- Read current description
- Identify why unrelated queries trigger it
- Add negative triggers ("Do NOT use for...")
- Make description more specific
- Test with 5 queries that should NOT trigger
Fix template:
# Before (over-triggers)
description: Processes documents for review
# After (specific + negative triggers)
description: >
Processes PDF legal documents for contract clause extraction and
compliance review. Use for legal contracts, NDAs, terms of service.
Do NOT use for general document editing, formatting, or non-legal PDFs.
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 First seen · 232 lines · 81 tokens per session scan A 4b4cd835f010
skill-forge-evolve is a skill published in the GitHub repository AgriciDaniel/skill-forge (166 stars, last pushed 4mo ago), licensed MIT. It adds 81 tokens to every session and 1,650 once invoked, about $0.0004 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
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
wiki
Initialize, adopt, and route work for a separate Obsidian knowledge vault through the portable claude-obsidian core. Use for vault setup, scaffolding, workspace selection, cross-project configuration, or choosing the correct wiki sub-skill. Triggers: /wiki, set up wiki, scaffold vault, create knowledge base, adopt…
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.