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-config-filenpx skills add plainlang/plain-forge --skill init-config-filegit 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.00127 | $0.05147 |
| Opus 5 | $0.00063 | $0.02573 |
| Sonnet 5 | $0.00025 | $0.01029 |
| Haiku 4.5 | $0.00013 | $0.00515 |
Grade A, and why
init-config-file 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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Config File
Always use the skill load-codeplain-reference to retrieve the full codeplain CLI reference (every flag, the config.yaml mapping, and the secrets / per-invocation keys that must never be written to config) — but only if you haven't done so yet. This skill assembles config.yaml from the valid CLI-derived keys, so the CLI reference is required.
This skill is the single authoritative writer of config.yaml for a ***plain project. Anything that ends up in config.yaml should go through this skill. The renderer (codeplain) reads each key listed below into the same argparse namespace it uses for CLI flags — so a value set in config.yaml is exactly equivalent to passing the corresponding --flag on the command line.
When to run
- End of
forge-plainPhase 3 / start of Phase 4 — after every test-script decision is locked in (unit tests, conformance tests, prepare-environment), before delegating toplain-healthcheck. - End of
add-feature— only when Phase 3 of the feature touched the testing surface (new script generated, script removed, template directory introduced). - End of any single-skill workflow that finalizes a script or template — e.g. after
implement-unit-testing-script,implement-conformance-testing-script,implement-prepare-environment-script,add-template, orcreate-import-module. - On demand — when the user asks "rebuild my config", "what valid keys are there", or you discover the config file is hand-edited / inconsistent.
If you only fixed a typo inside a .plain file and the testing surface didn't move, you do not need to re-run this skill — go straight to plain-healthcheck.
What this skill does
- Determines how many
config.yamlfiles the project needs (one per part — see Per-part split). - For each config, gathers the decided values from the current project state (existing scripts under
test_scripts/, the template directory, the build/dest folder choices). - Emits a clean, alphabetically-grouped
config.yamlcontaining only keys that are actually in use, using the canonical key names from the Valid keys reference. - Verifies that every
*-scriptvalue points at a file that exists on disk undertest_scripts/(or wherever the user placed it), using the same resolution rule the renderer uses: an absolute path (or a~path) is used as-is; a relative path inconfig.yamlresolves against the config file's directory. There is no other fallback — the renderer fails fast with aFileNotFoundErrorwhen a script path doesn't resolve to an existing file. - Hands off to
plain-healthcheckfor the full validation pass.
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 · 263 lines · 127 tokens per session scan A 8cdefc2092d1
init-config-file is a skill published in the GitHub repository plainlang/plain-forge (55 stars, last pushed 4d ago), licensed MIT. It adds 127 tokens to every session and 5,147 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.
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…
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.