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 plainlang/plain-forge --skill load-plain-referencegit 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/load-plain-reference)<a href="https://agentmods.dev/skills/plainlang/plain-forge/load-plain-reference"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/load-plain-reference/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/plainlang/plain-forge/load-plain-reference"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/load-plain-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 20 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00070 | $0.00969 |
| Opus 5.5 | $0.00028 | $0.00388 |
| Sonnet 5.5 | $0.00014 | $0.00194 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
load-plain-reference 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 20d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Load the ***plain reference
Load only the rules and references required for the current task. Files under ../../rules/ are
the source of truth for .plain syntax and authoring constraints. Do not restate or override them.
First, confirm the rules about to be loaded are current. On the first invocation of this skill in
a session, invoke check-forge-version before loading any rule file. A stale plain-forge ships stale
rules, so every routing decision below inherits its verdict.
If that skill reports a stale or unconfirmed install, tell the user clearly that authoring on an
outdated plain-forge is not recommended and ask them to run npx plain-forge update before
continuing — the rules routed to below may not match what the current renderer expects.
Give them the choice rather than blocking: if they decline, continue with the rules on disk and treat
the stale install as the first suspect for anything that later behaves unexpectedly.
Skip the check on later invocations in the same session, and skip it when the network is unavailable.
1. Account for rules already loaded
- In Claude Code, applicable
.claude/rules/*.mdfiles are loaded natively. Do not read those rule files again. - In another agent, do not reread a rule whose full content is already present in the current context.
- Otherwise, read the applicable files from the routing table below before inspecting or changing
.plaincontent.
2. Load applicable authoring rules
All paths are relative to this SKILL.md.
| Task or content | Rule files |
|---|---|
| New module, file skeleton, section placement, or comments | ../../rules/module-structure.md |
Moving facts between sections (see resolve-section-ownership) |
../../rules/module-structure.md, plus the rule file of each section involved |
| Definitions or concept usage | ../../rules/definitions.md |
| Functional specs or acceptance tests | ../../rules/func-specs.md |
| Implementation requirements or unit tests | ../../rules/impl-reqs.md |
| Test requirements or conformance tests | ../../rules/test-reqs.md |
import modules |
../../rules/import-modules.md |
requires modules |
../../rules/requires-modules.md |
required_concepts |
../../rules/required-concepts.md |
exported_concepts |
../../rules/exported-concepts.md |
Linked files or resources/ |
../../rules/linked-resources.md |
Any .plain text or example |
../../rules/bullet-continuation.md, ../../rules/concise-specs.md |
| Drafting or trimming spec wording, or reviewing a spec for verbosity | ../../rules/concise-specs-examples.md |
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.
- 20d ago Changed · -1 lines · -5 tokens per session 9d7c3aa1c987
- 1mo ago First seen · 90 lines · 75 tokens per session scan A c5ebad2c6cfe
load-plain-reference is a skill published in the GitHub repository plainlang/plain-forge (79 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 969 once invoked, about $0.0003 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-30.
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…