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 skills add luiseiman/dotforge --skill openclawgit clone --depth 1 https://github.com/luiseiman/dotforgeWrote 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.
[](https://agentmods.dev/skills/luiseiman/dotforge/openclaw)<a href="https://agentmods.dev/skills/luiseiman/dotforge/openclaw"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/openclaw/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/luiseiman/dotforge/openclaw"><img src="https://agentmods.dev/badge/skills/luiseiman/dotforge/openclaw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00982 |
| Opus 5.5 | $0.00008 | $0.00393 |
| Sonnet 5.5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
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 17d 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 — 130 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.local.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 |
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:
# Look up path from registry
python3 -c "
import yaml
reg = yaml.safe_load(open('$DOTFORGE_DIR/registry/projects.local.yml'))
for p in reg['projects']:
if p['name'].lower() == '<project_name>'.lower():
print(p['path'])
break
"
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.
- 17d ago Changed · -1 lines a633249c1737
- 1mo 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 18d ago), licensed MIT. It adds 19 tokens to every session and 982 once invoked, about $0.0001 per session on Opus 5.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
zephermine
Creates a persisted, sectionized implementation artifact suite through research, stakeholder interviews, domain analysis, database and API design, and multi-LLM review. Use for feature or product plans consumed by downstream implementation and QA. Prefer lightweight native plan/interview workflows for small tasks; on…
agent-team
A guide for coordinating a team of coding agents working on one task. It covers when to split work into parallel assignments, how a lead agent coordinates them, and how to record shared knowledge.
clio
A final-review and document-production workflow. It checks whether a process is ready to proceed, extracts source-based diagrams, and creates documents such as product requirements, technical documentation, and manuals.
design-plan
A design-system planning and implementation guide for frontend projects. A design system is a shared set of visual rules, reusable components, and accessibility practices for building consistent user interfaces.
frontend-design
A frontend design and implementation guide for turning a visual design plan into a working web interface. It also provides fallback guidance when an official design plugin is unavailable.
argos
A software inspection skill that checks an implementation against design documents such as API specifications, quality-assurance scenarios, flow diagrams, and other project specifications.