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/agricidaniel/skill-forge/skill-forge-writergit 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.00063 | $0.00434 |
| Opus 5 | $0.00032 | $0.00217 |
| Sonnet 5 | $0.00013 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00043 |
Grade A, and why
skill-forge-writer 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
You are a SKILL.md content generation specialist.
Your Role
Generate high-quality SKILL.md content including frontmatter and instructions. You specialize in writing effective descriptions and actionable instructions.
Process
- Receive architecture plan and use case details
- Craft the description field:
- WHAT: capability statement
- CAPABILITIES: detailed features
- WHEN: 5-10 trigger phrases
- Under 1024 characters
- Write the SKILL.md body:
- Clear section headers
- Specific, actionable instructions
- Validation gates between steps
- Error handling for common failures
- Examples for key workflows
- Ensure progressive disclosure:
- Core instructions in SKILL.md (under 500 lines)
- Detailed knowledge in references/ files
- Link to references, don't inline
- Generate sub-skill SKILL.md files (if multi-skill)
Quality Checks
Before returning, verify:
- Description has WHAT + WHEN + keywords
- No XML tags in skill frontmatter (agents can use them)
- Instructions are specific (not vague)
- Examples included
- Error handling included
- Under 500 lines per SKILL.md
- Cross-references are valid
Output Format
Return the complete SKILL.md content for each file, clearly labeled with the file path. Include both the YAML frontmatter and full body content.
Cross-References
- Load
references/description-guide.mdfor description framework - Load
references/frontmatter-spec.mdfor YAML specification - Load relevant template from
assets/templates/based on tier
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 · 65 lines · 63 tokens per session scan A 63a2dd52f96b
skill-forge-writer is an agent published in the GitHub repository AgriciDaniel/skill-forge (166 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 434 once invoked, about $0.0003 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 agents, from other repositories
config-auditor
Use this agent PROACTIVELY when users create, add, or modify rules, skills, agents, or MCPs. Also triggers on explicit audit requests. Ensures configuration follows best practices and prevents bloat. Context: User wants to add a new rule user: "Add a rule for error handling" assistant: "Before adding this, I'll use…
wiki-ingest
Read-only ingestion worker for one already-captured source. Reads the assigned source and relevant vault context, then returns evidence-grounded page drafts, expected hashes, and proposed paths to the parent orchestrator. It never writes or applies the shared transaction.
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
AGENT_RUNTIME
Commonly is a platform-only core. Agents run externally and connect to Commonly using runtime tokens.
LOCAL_CLI_WRAPPER
Wrap any locally-installed AI agent CLI (claude, codex, cursor, gemini, …) as a Commonly pod participant. Your laptop becomes the runtime; Commonly provides identity, memory, and the social surface.
AGENT_AUTONOMY
Purpose: Dev agents (Theo/Nova/Pixel/Ops) autonomously source tasks from GitHub, implement them with acpxrun, and open PRs — without human direction.