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/harshanandak/forge/kernelnpx skills add harshanandak/forge --skill kernelgit clone --depth 1 https://github.com/harshanandak/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.00240 | $0.02671 |
| Opus 5 | $0.00120 | $0.01336 |
| Sonnet 5 | $0.00048 | $0.00534 |
| Haiku 4.5 | $0.00024 | $0.00267 |
Grade A, and why
kernel 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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge kernel surface
Forge is a TDD-first workflow harness. The agent-facing surface is skills + the
forge CLI — there are no slash-command files. This umbrella skill is the
entry point: it tells you which stage skill to use and which forge verb runs
each day-to-day operation. Every skill is a thin guide over a real forge
command; the CLI remains the implementation, the skills are the surface.
Stage skills (the TDD ladder)
The default workflow is a configurable ladder of per-stage skills. Use the whole flow when it fits, or invoke an individual stage when the active plan permits a smaller path.
| Stage | Skill | Purpose |
|---|---|---|
| utility | status |
Check current context, active work, recent completions |
| 1 | plan |
Design intent → research → branch + worktree + task list |
| 2 | dev |
Subagent-driven TDD per task (implementer → spec → quality review) |
| 3 | validate |
Type check, lint, code review, security, tests — all fresh output |
| 4 | ship |
Push branch and open the PR with design-doc reference |
| 5 | review |
Address ALL PR feedback (GitHub Actions, Greptile, SonarCloud) |
| 6 | verify |
Post-merge health check (CI on main, close issues) |
Pre-merge gate (not a numbered stage): before merge, finish the doc updates on
the feature branch and confirm CI is green, then hand off the PR for manual merge.
The gate is embedded in ship and review — it is not a standalone skill.
Utility skills outside the linear ladder: research (deep web research),
rollback (safe revert operations), sonarcloud (code-quality queries),
shepherd (cross-harness PR monitoring).
Procedure skills (reusable operations any stage/agent embeds): claim-safety
(claim an issue and PROVE you own the lease via forge issue owns <id> before
mutating it — a claim returning ok:true does not by itself prove ownership).
status → plan → dev → validate → ship → review → verify
Chain map (each skill declares its successor)
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 205 lines · 240 tokens per session scan A f474f2e73461
kernel is a skill published in the GitHub repository harshanandak/forge (4 stars, last pushed 2d ago), licensed MIT. It adds 240 tokens to every session and 2,671 once invoked, about $0.0012 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…