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/codejunkie99/agentic-stack/skillforgenpx skills add codejunkie99/agentic-stack --skill skillforgegit clone --depth 1 https://github.com/codejunkie99/agentic-stackWhat 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.00002 | $0.00400 |
| Opus 5 | $0.00001 | $0.00200 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
skillforge 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 yesterday.
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
Skillforge — the skill that creates skills
When a new capability is needed:
- Check for duplicates. Read
skills/_index.md. If a similar skill exists, extend it instead of creating a new one. - Check memory. Read
memory/semantic/LESSONS.mdfor related patterns. - Draft the skill. Create
skills/<name>/SKILL.mdwith:- YAML frontmatter (name, version, triggers, tools, preconditions, constraints)
- Plain-language instructions (destinations and fences, not driving directions)
- A self-rewrite hook at the bottom
- Register it. Add an entry to
skills/_index.mdand append a JSON line toskills/_manifest.jsonl. - Log it. Append a record to
memory/semantic/DECISIONS.mdexplaining why this skill was created.
What good skills look like
- State the destination ("verify tests pass before commit"), not the exact command sequence.
- Include 2–3 examples of correct behavior when it clarifies intent.
- Include 1 example of a failure and what was learned from it.
- Keep the whole file under 100 lines.
Self-rewrite hook
After every 5 skills created, or on any failed creation:
- Read the last 5 skillforge entries from episodic memory.
- If better trigger patterns or constraint structures have emerged, update this file and the template it implies.
- Commit:
skill-update: skillforge, <one-line reason>.
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.
- yesterday First seen · 38 lines · 2 tokens per session scan A 999e4de4c98d
skillforge is a skill published in the GitHub repository codejunkie99/agentic-stack (2,241 stars, last pushed 25d ago), licensed Apache-2.0. It adds 2 tokens to every session and 400 once invoked, about $0.0000 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.