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 jslee124/forge --skill forge-plugin-creatorgit clone --depth 1 https://github.com/jslee124/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/jslee124/forge/forge-plugin-creator)<a href="https://agentmods.dev/skills/jslee124/forge/forge-plugin-creator"><img src="https://agentmods.dev/badge/skills/jslee124/forge/forge-plugin-creator/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/jslee124/forge/forge-plugin-creator"><img src="https://agentmods.dev/badge/skills/jslee124/forge/forge-plugin-creator.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.00058 | $0.00738 |
| Opus 5.5 | $0.00023 | $0.00295 |
| Sonnet 5.5 | $0.00012 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
forge-plugin-creator 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 1mo 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge plugin creator
Use this workflow for Forge plugin work. This Skill is instruction text, not a plugin: it is never imported or executed and grants no filesystem, process, network, model, or approval capability. A generated plugin is trusted in-process JavaScript with the local privileges of Forge, so activation and trust must remain explicit.
Required inspection
Before generating or changing code:
- Inspect the active
plugin.jsonschema inpackages/plugin-api/src/schema.ts, the API types inpackages/plugin-api/src/types.ts, andPLUGIN_API_VERSIONwhen working in the Forge repository. - Inspect the nearest maintained example under
examples/plugins/that uses the requested extension point. - Outside the Forge repository, load the registered
references/plugin-api.mdresource supplied with this Skill. Treat its version as matching the installed CLI. - Load a registered template only as a starting point. Adapt it to the task; do not copy capabilities or risks that are not needed.
Do not claim an API, capability, or hook exists without one of those sources.
Workflow
- Choose the scope: user plugins live at
$FORGE_HOME/plugins/<name>/; project plugins live at<workspace>/.forge/plugins/<name>/and require canonical project trust. - Create a strict manifest and dependency-free
.mjsentry when practical. The manifest name must equal its directory name. - Declare only the capabilities actually used. A network-risk tool also
requires
network:access. - Give every model-callable input a strict, bounded schema and label its real
external effect:
read,write,process,network, ormodel. - Keep tool execution inside Forge's proposal, schema validation, policy, approval, execution, result, event, and trace path. Never perform the work from a prompt hook or observer to evade that path.
- Add focused tests that activate through the real plugin host when the Forge repository is available. Test invalid input and capability/trust boundaries, not only the success path.
- Document enablement or
forge plugins trust; never silently edit trust state or imply that repository content is trusted merely because a Skill selected it.
What ships with it
4 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.
- 1mo ago First seen · 71 lines · 58 tokens per session scan A a925ac726a42
forge-plugin-creator is a skill published in the GitHub repository jslee124/forge (4 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 738 once invoked, about $0.0002 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…