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-if-func-spec-too-complexgit 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-if-func-spec-too-complex)<a href="https://agentmods.dev/skills/plainlang/plain-forge/analyze-if-func-spec-too-complex"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/analyze-if-func-spec-too-complex/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-if-func-spec-too-complex"><img src="https://agentmods.dev/badge/skills/plainlang/plain-forge/analyze-if-func-spec-too-complex.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.00079 | $0.01833 |
| Opus 5.5 | $0.00032 | $0.00733 |
| Sonnet 5.5 | $0.00016 | $0.00367 |
| Haiku 4.5 | $0.00008 | $0.00183 |
Grade A, and why
analyze-if-func-spec-too-complex 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze If Functional Spec Is Too Complex
Always use the skill load-plain-reference to retrieve the ***plain syntax rules — but only if you haven't done so yet.
Why This Matters
The renderer enforces a hard complexity limit: each functional spec must imply a maximum of 200 changed lines of code. If a spec exceeds this, the renderer rejects it with "Functional spec too complex!" and the spec must be broken down. Catching this before insertion saves a failed render cycle.
Input
A drafted functional spec (not yet inserted into the file), plus the full context of the .plain file it will be added to — definitions, implementation reqs, and existing functional specs.
Workflow
- Read the full
.plainfile (and anyrequires/importmodules) to understand the current codebase context — what already exists and what the new spec builds on. - Read the drafted functional spec carefully.
- Run the complexity analysis using the checklist below.
- Output the verdict and nothing else — either
ACCEPTABLEorTOO COMPLEX. No reasoning, no LOC estimate, no breakdown.
Complexity Analysis Checklist
Work through each indicator. A single "yes" does not automatically mean the spec is too complex, but multiple "yes" answers are a strong signal.
0. First-Spec Bootstrap Cost
Is this the first functional spec in a new root module with no implementation baseline supplied by
requires? If so, include the implicit cost of creating the project structure, package metadata,
framework configuration, entry point, initial source files, and unit-test infrastructure.
The first spec must be substantially simpler than a later spec. It should expose one minimal,
deterministic capability that can be invoked and tested. Setup without an observable result is not
acceptable, but combining bootstrap work with persistence, integrations, multiple interfaces,
branching workflows, or cross-cutting behavior is a strong TOO COMPLEX signal.
1. Number of Distinct Behaviors
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 · 213 lines · 79 tokens per session scan A 941757e5d779
analyze-if-func-spec-too-complex is a skill published in the GitHub repository plainlang/plain-forge (79 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,833 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…