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 analyze-func-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/analyze-func-specs)<a href="https://agentmods.dev/skills/plainlang/plain-forge/analyze-func-specs"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/analyze-func-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/analyze-func-specs"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/analyze-func-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.00073 | $0.01245 |
| Opus 5.5 | $0.00029 | $0.00498 |
| Sonnet 5.5 | $0.00015 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
analyze-func-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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Functional Specs
Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.
Input
A set of two or more functional specs to check against each other. Callers typically supply one of:
- A whole
***functional specs***section to self-check. - A new spec (or batch of new specs) plus the existing specs from the same file and any
requiresmodules. - An explicit list of spec snippets the user wants compared.
Each spec must be identifiable. If the caller didn't label them, assign stable identifiers in order of appearance: S1, S2, S3, …. Use those identifiers in the output. If the caller provided their own IDs or quoted snippets, use those instead and keep them verbatim.
The skill also needs the ***definitions*** section (and any imported definitions) so referenced :Concepts: can be resolved.
Workflow
- Read all input specs and the relevant
***definitions***so every:Concept:is understood. - Establish chronological order across the batch. Earlier specs are considered to have been rendered first; later specs are evaluated with the earlier ones in context. If the caller already provided an order, preserve it.
- Generate the pair list. Enumerate every unordered pair
(Sᵢ, Sⱼ)withi < j. Skip pairs where the two specs share no:Concept:and no overlapping subject — they are trivially compatible and listing them adds noise. - Run the conflict analysis below on each remaining pair. Use the same checklist that the legacy
analyze-2-func-specsskill used, but apply it pair by pair across the batch in a single pass — do not require the caller to invoke the analyzer once per pair. - Record every CONFLICTING pair. Compatible pairs are not listed individually; only the conflicts are emitted.
- Output the verdict in the format below. No reasoning, no category labels, no resolution suggestions.
Conflict Analysis Checklist (applied per pair)
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 · 125 lines · 73 tokens per session scan A abb4b249b6c6
analyze-func-specs is a skill published in the GitHub repository plainlang/plain-forge (79 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,245 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…