skill-forge

skill-forge is a skill for Claude Code, Codex from svy04/ballast. It costs 67 tokens per session (700 once invoked), scanned A, original, MIT.

A method for turning a successfully completed and verified procedure into a reusable skill file for future tasks.

In plain words
What is it for?
Use it after a repeatable deployment, migration, test fix, or similar multi-step task has worked and been verified.
Why use it?
It prevents hard-won troubleshooting steps from being forgotten or repeated from scratch. Only procedures that are likely to recur and have been checked as successful are recorded.

Skill for Claude CodeCodex

Part of the ballast plugin — 16 skills, 4 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/svy04/ballast/skill-forge
Any agent
npx skills add svy04/ballast --skill skill-forge
Clone the repo
git clone --depth 1 https://github.com/svy04/ballast

Made for: Claude Code, Codex.

Or install ballast, the plugin that ships this one along with the rest of its 16 skills, 4 hooks.

Wrote 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.

agentmods badge for skill-forge

README.md
[![agentmods](https://agentmods.dev/badge/skills/svy04/ballast/skill-forge.svg)](https://agentmods.dev/skills/svy04/ballast/skill-forge)
Your own site
<a href="https://agentmods.dev/skills/svy04/ballast/skill-forge"><img src="https://agentmods.dev/badge/skills/svy04/ballast/skill-forge.svg" alt="Measured on agentmods" height="20"></a>
Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 700 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.00700
Opus 5 $0.00034 $0.00350
Sonnet 5 $0.00013 $0.00140
Haiku 4.5 $0.00007 $0.00070

Measured 5d ago against content hash b07f84122861, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skill-forge 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 5d 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.

skills/skill-forge/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill forge

Some tasks are solved once and then re-solved forever: the deploy that took an afternoon of trial and error, the migration that only worked in one specific order, the flaky test that needed three environment tweaks. The solving was real work; letting it evaporate means paying for it again. When a procedure has been driven from start to finish and the success was checked, not declared, forge it into .claude/skills/<name>/SKILL.md — the next similar task starts where this one ended.

When to forge

Both conditions, not either:

  1. It will recur. The task shape is likely to come back — same project or same class of problem. One-off procedures stay in the session log.
  2. Success was verified. A check passed: the build is green, the endpoint responds, the output was inspected. "It seemed to work" forges nothing — a skill built on an unverified run teaches the next session a guess.

What goes in the file

The skill file records the procedure as it actually ran, not as it should have run in theory:

  • When to use — the task shape that triggers it, specific enough that the wrong task won't match.
  • Procedure — the steps in the order that worked, including the traps hit along the way (step 3 fails silently if the cache wasn't cleared first is the most valuable line in the file).
  • Verified — the date the procedure last succeeded.
  • Evidence — what confirmed success: the test that passed, the file that existed, the output that was checked. This line is what separates a skill from a hopeful note.
  • Source — the memory/knowledge/ entry the procedure rests on, when there is one. Include this line only in that case; it is what makes the third freshness trigger below reachable.

Frontmatter follows the usual shape: name matching the directory, description saying what it does and when to use it.

Relation to pin

pin promotes a one-line rule — a correction or preference that should arrive with matching messages. skill-forge promotes an entire procedure — multiple steps, ordering, traps. When a lesson fits in a sentence, pin it; when it only fits in a walkthrough, forge it. A forged skill often yields one pin as a by-product: the single sharpest trap, delivered even when the skill isn't opened.

Read the full file on GitHub · 40 lines

Changes

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.

  1. 5d ago First seen · 40 lines · 67 tokens per session scan A b07f84122861

Subscribe to this mod's changes

skill-forge is a skill published in the GitHub repository svy04/ballast (71 stars, last pushed 10d ago), licensed MIT. It adds 67 tokens to every session and 700 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.

Related

Other skills, from other repositories

alive:demo

Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.

alivecontext/alive · 52 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

alive:session-history

Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…

alivecontext/alive · 76 tokens

alive:world

The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.

alivecontext/alive · 63 tokens

alive:mine-for-context

Deep context extraction from source material. Creates reference bundles, builds extraction plans, tracks what's been extracted, and discovers new targets — people, subjects, patterns, connections. The archaeologist that turns raw sources into structured knowledge. Can be invoked by alive:session-history for targeted…

alivecontext/alive · 63 tokens

alive:settings

The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…

alivecontext/alive · 84 tokens