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 add-functional-specsgit 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/add-functional-specs)<a href="https://agentmods.dev/skills/plainlang/plain-forge/add-functional-specs"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/add-functional-specs/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/add-functional-specs"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/add-functional-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.01999 |
| Opus 5.5 | $0.00039 | $0.00800 |
| Sonnet 5.5 | $0.00019 | $0.00400 |
| Haiku 4.5 | $0.00010 | $0.00200 |
Grade A, and why
add-functional-specs 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Functional Specs
Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.
When to Use
- The user asks for several functional specs to be added in one go (e.g. "add these three specs", "spec out this feature in a few bullets").
- A higher-level skill or workflow (
forge-plain,add-feature,debug-specs) needs to author a tight group of related specs. - Anywhere you would otherwise be tempted to write more than one functional spec without running per-spec analysis.
If you only need to add a single spec, use the add-functional-spec skill instead. Either way, never edit the ***functional specs*** section by hand — every new entry must go through one of these two skills so the complexity and conflict checks actually run.
Workflow
This skill is add-functional-spec applied one spec at a time, in order, with no shortcuts. The batch never escapes per-spec rigor.
- Identify the target
.plainfile. If ambiguous, ask the user. - Read the entire file to understand existing definitions, implementation reqs, and all current functional specs (including those reachable via
import/requires). - Draft all the specs you intend to add, in the chronological order they should appear. Keep the drafts in a working list — nothing is inserted yet. Run the review pass in
concise-specs.mdover every draft before continuing; trim each to the shortest wording that keeps every fact. - For each drafted spec, in order:
- Analyze complexity. Run
analyze-if-func-spec-too-complexon the spec. If the verdict isTOO COMPLEX, runbreak-down-func-spec, replace the entry in the working list with the resulting smaller specs (preserving order), and restart this step on the first of the replacements. - Check for conflicts. Run
analyze-func-specsonce with this single input set:- the new spec, plus
- every existing functional spec in the file and its
requireschain, plus - every spec from this batch that has already been inserted.
- Analyze complexity. Run
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 · 120 lines · 97 tokens per session scan A 1948ef2adace
add-functional-specs is a skill published in the GitHub repository plainlang/plain-forge (79 stars, last pushed yesterday), licensed MIT. It adds 97 tokens to every session and 1,999 once invoked, about $0.0004 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…