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/luiseiman/dotforge/openclawnpx skills add luiseiman/dotforge --skill openclawgit clone --depth 1 https://github.com/luiseiman/dotforgeWhat 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.00019 | $0.00991 |
| Opus 5 | $0.00010 | $0.00495 |
| Sonnet 5 | $0.00004 | $0.00198 |
| Haiku 4.5 | $0.00002 | $0.00099 |
Grade A, and why
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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge — dotforge bridge for OpenClaw
Execute dotforge configuration management commands from any OpenClaw channel (WhatsApp, Telegram, Slack, etc.).
How it works
This skill bridges OpenClaw to dotforge by running claude CLI in the target project directory. All /forge subcommands are available.
Environment
DOTFORGE_DIR— path to dotforge repo (required)- Default project: uses
DOTFORGE_DIRitself if no project specified
Command format
/forge <command> [project:<name>]
If project:<name> is provided, look up the project path from $DOTFORGE_DIR/registry/projects.yml and execute in that directory.
If no project specified, use current context or ask the user.
Available commands
Read-only (safe from any channel)
| Command | What it does |
|---|---|
status |
Multi-project dashboard with scores and trends |
version |
Show dotforge version |
pipeline |
Practices lifecycle status |
inbox |
List pending practices |
Per-project (require project context)
| Command | What it does |
|---|---|
audit |
Score project configuration 0-10 |
diff |
Show pending changes since last sync |
insights |
Analyze past sessions |
rule-check |
Detect inert rules |
Mutation (ask for confirmation before executing)
| Command | What it does |
|---|---|
sync |
Update project config against template |
bootstrap |
Initialize .claude/ in a project |
capture "text" |
Record a practice in inbox |
update |
Process practices pipeline |
watch |
Check for upstream changes |
scout |
Review curated repos |
reset |
Restore .claude/ from template |
benchmark |
Compare full vs minimal config |
Execution
Step 1: Parse command
Extract:
subcommand— the forge action (audit, status, sync, etc.)project— optional project name fromproject:<name>suffixargs— any remaining arguments
Step 2: Resolve project path
If a project name is provided:
What ships with it
7 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 · 131 lines · 19 tokens per session scan A 404a265dfc08
forge is a skill published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 991 once invoked, about $0.0001 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
scaffold
Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
find-opps
Find new directions for an ops project — adjacent opportunities, strategic gaps, preparatory research. Use when known work is well-mined and you need to look outward.
prioritize
Pick 2–3 independent ops tasks from active plans and backlog for autonomous execution, weighing impact, feasibility, and project goals.
factory-api
API conventions for both server actions and tRPC builds. Covers the decision between them, per-mutation Zod input schemas, central router composition, pagination shape, multi-field search via Drizzle ilike + or(), mutation lifecycle hooks, conditional query enabling, stale-time defaults, error response shape and…
factory-ci
CI and pull-request review conventions. One canonical .github/workflows/ci.yml is the merge gate (typecheck, lint, test, build, claude-review); branch protection's required-checks list matches the job list 1:1; anthropics/claude-code-action@v1 reviews every PR against the factory-pitfalls.md checklist as a required…
factory-design
Design-system discipline distilled across builds. Semantic token vocabulary (name intent, not palette position), CSS variables bridged into Tailwind, dark/light as a variable swap, single- vs two-layer token systems, component primitives as token consumers, when to promote a repeated utility cluster into a primitive…