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/plain-healthchecknpx skills add plainlang/plain-forge --skill plain-healthcheckgit clone --depth 1 https://github.com/plainlang/plain-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/plainlang/plain-forge/plain-healthcheck)<a href="https://agentmods.dev/skills/plainlang/plain-forge/plain-healthcheck"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/plain-healthcheck.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.00131 | $0.02919 |
| Opus 5 | $0.00066 | $0.01460 |
| Sonnet 5 | $0.00026 | $0.00584 |
| Haiku 4.5 | $0.00013 | $0.00292 |
Grade A, and why
plain-healthcheck 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 5d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plain Healthcheck
Always use the skill load-codeplain-reference to retrieve the full codeplain CLI reference (every flag, path-resolution rules, config.yaml mapping, render banners, exit codes), and the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet. This skill runs codeplain … --dry-run and validates every config.yaml, so the CLI reference is required.
When to run
Run this skill **whenever anything in the *plain project is finalized and the project is about to be left in a state the user (or another skill) might render from. That includes, but is not limited to:
- End of
forge-plain(Phase 4) — before presenting the render command. - End of
add-feature(Phase 3 final review) — before declaring the feature done. - End of
debug-specs— after applying a fix, before telling the user to re-render. - After finalizing any single edit that changes the renderable surface — e.g. after
add-concept,add-functional-spec,add-functional-specs,add-implementation-requirement,add-test-requirement,add-acceptance-test,add-template,add-resource,resolve-spec-conflict,break-down-func-spec,consolidate-concepts,refactor-module,create-import-module,create-requires-module, or any of theimplement-*-testing-scriptskills. - After hand-editing a
.plainfile, aconfig.yaml, or anything undertest_scripts/. - On demand — whenever the user asks whether the project is in a renderable state.
The healthcheck is not a forge-plain-only step. Treat it as the default closing move for any workflow that finalizes something in the project.
Do not skip this skill because "the dry-run passed earlier" — config.yamls, scripts, and specs can all drift between runs. The healthcheck is cheap; rendering against stale specs is expensive.
Workflow
The skill is a detect → fix → re-run loop. It does not stop at the first failure; it surfaces everything wrong, fixes what it can, and only returns when either everything passes or a gap genuinely requires user input.
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.
- 5d ago First seen · 133 lines · 131 tokens per session scan A ebae64e2dc7b
plain-healthcheck is a skill published in the GitHub repository plainlang/plain-forge (55 stars, last pushed 2d ago), licensed MIT. It adds 131 tokens to every session and 2,919 once invoked, about $0.0007 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…