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/plainlang/plain-forge/init-plain-projectnpx skills add plainlang/plain-forge --skill init-plain-projectgit clone --depth 1 https://github.com/plainlang/plain-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.00114 | $0.01802 |
| Opus 5 | $0.00057 | $0.00901 |
| Sonnet 5 | $0.00023 | $0.00360 |
| Haiku 4.5 | $0.00011 | $0.00180 |
Grade A, and why
init-plain-project 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.
Init Plain Project
Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.
Scope
This skill is intentionally minimal. It produces a runnable project skeleton — not a complete spec. No ***definitions*** sections are written by this skill — not in the template module, not in the top module. No functional specs, no concepts, no acceptance tests, no dry-run validation. The user will fill those in afterwards with add-feature, add-concept, add-functional-spec, etc.
What this skill writes:
template/base.plain— an import module with the project's base***implementation reqs***and***test reqs***.<project>.plain— a top-level module that importsbase. Frontmatter only — no body sections. The user adds***functional specs***later.test_scripts/run_unittests_<lang>.<sh|ps1>— always.test_scripts/run_conformance_tests_<lang>.<sh|ps1>— only if conformance testing is enabled.test_scripts/prepare_environment_<lang>.<sh|ps1>— only if conformance testing is enabled and the user opts in.config.yamlat the project root — wired to whichever scripts were generated.
What this skill does not do:
- Run
codeplain --dry-runorplain-healthcheck. - Author concepts, functional specs, or acceptance tests.
- Probe the host environment (
check-plain-envis a separate step the user can run later).
Workflow
1. Ask the project basics
Use AskUserQuestion for one tight batch covering:
- Project name — used as the top module filename and as
:AppName:later. Free-form. - Base technology — programming language and primary framework (e.g. Python + FastAPI, Node.js + Express, Go + net/http, Java + Spring Boot). Offer the most common stacks plus free-form.
- Project kind — CLI tool, web app, REST API / backend service, library, desktop app, mobile app, other. Offer the common kinds plus free-form.
Follow up with a free-form prompt for anything the options didn't cover (e.g. specific Python version, monorepo layout).
What ships with it
1 file 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 · 114 tokens per session scan A 18f953981f94
init-plain-project is a skill published in the GitHub repository plainlang/plain-forge (55 stars, last pushed 4d ago), licensed MIT. It adds 114 tokens to every session and 1,802 once invoked, about $0.0006 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.
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…