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/albertbuchard/forge/forge-openclawnpx skills add albertbuchard/forge --skill forge-openclawgit clone --depth 1 https://github.com/albertbuchard/forgeWrote 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/albertbuchard/forge/forge-openclaw)<a href="https://agentmods.dev/skills/albertbuchard/forge/forge-openclaw"><img src="https://agentmods.dev/badge/skills/albertbuchard/forge/forge-openclaw.svg" alt="Measured on agentmods" 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 | $0.00259 | $0.26127 |
| Opus 5 | $0.00130 | $0.13064 |
| Sonnet 5 | $0.00052 | $0.05225 |
| Haiku 4.5 | $0.00026 | $0.02613 |
Grade A, and why
forge-openclaw-plugin 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 3d 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 — 1,339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge is the user's structured system for planning work, doing work, reflecting on patterns, and keeping a truthful record of what is happening. Use it when the user is clearly working inside that system, or when they are describing something that naturally belongs there and would benefit from being stored, updated, reviewed, or acted on in Forge. Keep the conversation natural first. Do not turn every message into intake. When a real Forge entity is clearly present, name the exact entity type plainly, help with the substance of the conversation, and then offer Forge once, lightly, if storing it would genuinely help.
Live Contract And Missing-Information Gate
Before the first Forge read or write in a session, call
forge_get_agent_onboarding. Match the user's target to one exact
entityCatalog[] entry or one published specialized surface. Treat that live entry's
classification, minimumCreateFields, fieldGuide, questionFlow,
preferredReadPath, preferredMutationPath, and preferredMutationTool as the
current contract. The bundled playbooks guide the conversation; they do not override
the live schema or route map.
Build a private missing-information diff before asking anything:
- remove details the user already supplied
- remove optional fields and published defaults that do not change meaning, accountability, timing, retrieval, safety, or route selection
- on update, read the current record first and preserve every field the user did not ask to change
- ask one Psyche question at a time; for logistical records, one compact question may group inseparable details such as start, end, and timezone
- act when no blocking ambiguity remains instead of asking a polished extra question
If the target is absent from live onboarding, refresh once. If it is still absent, report a Forge contract mismatch and do not invent an entity type, field, tool, or nearby route.
Project Management Hierarchy Rule
Forge project management is explicit and hierarchical:
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.
- 3d ago First seen · 1,339 lines · 259 tokens per session scan A 6808d15cdcb0
forge-openclaw-plugin is a skill published in the GitHub repository albertbuchard/forge (23 stars, last pushed 6d ago), licensed Apache-2.0. It adds 259 tokens to every session and 26,127 once invoked, about $0.0013 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…