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 ymm-oss/fsl --skill fsl-design-reviewgit clone --depth 1 https://github.com/ymm-oss/fslWrote 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/ymm-oss/fsl/fsl-design-review)<a href="https://agentmods.dev/skills/ymm-oss/fsl/fsl-design-review"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/fsl-design-review/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/ymm-oss/fsl/fsl-design-review"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/fsl-design-review.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.00155 | $0.02643 |
| Opus 5 | $0.00077 | $0.01321 |
| Sonnet 5 | $0.00031 | $0.00529 |
| Haiku 4.5 | $0.00015 | $0.00264 |
Grade A, and why
fsl-design-review 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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FSL Design Exploration — A Procedure for Translating Design Decisions into Contract-Conformance Checks
The core is the following 5-step procedure. Design principles (SOLID etc.) are not the starting point of the procedure; they appear as judgment lenses at each step. This skill's job is to translate "is this design good?" into "does this design conform to the frozen contract?" and have fslc answer with counterexamples.
Prerequisite: FSL syntax, verification commands, and repair protocol follow
the fsl skill and its topic-specific references. This skill supplies only the
procedure and the interpretation of results.
If the user needs a new design-layer .fsl written before review, use
fsl-design for authoring and return here for review/proposal judgment.
Working examples: specs/bank.fsl + bank_impl.fsl + bank_refines.fsl
(refinement), seat_booking_* (state-tag-dependent mappings),
specs/bank_system.fsl (compose).
Procedure
Step 1 — Translate the design question into the language of contracts
Design questions almost always fall into one of four shapes: comparing new design proposals / adding a variant or extension / reviewing a change to an existing design / judging substitutability. In every shape, what you identify is the same:
- The open part: what may change (variants, extension points, the changed site)
- The closed part = the contract: what must not break (invariants, guards, externally observable state)
Lens — OCP: decide the "range you close" here. DIP: what abstraction should the design proposals all depend on in common. Align with the user on the candidate contracts as a bullet list before proceeding (do not create a deliverable file; chat is fine).
Do not infer the open/closed boundary, extension points, substitutability contract, variant roster, or action correspondence from general design taste. If the source material does not say what must remain stable or how a detail action maps to an abstract action, ask. A refinement proof is only meaningful for the contract the human agreed to freeze.
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.
- 9d ago First seen · 176 lines · 155 tokens per session scan A 0fb7624bfa61
fsl-design-review is a skill published in the GitHub repository ymm-oss/fsl (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 155 tokens to every session and 2,643 once invoked, about $0.0008 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
python-style
Validate Python code against style and architectural conventions.
Create, restyle, inspect, and visually verify polished PDF documents. Use when the user asks to create a PDF, turn supplied content into a PDF, improve an existing PDF, review PDF layout, or deliver a professional report, brief, handout, or printable document as a .pdf file.
architecture-diagrams
Author and visually review evidence-based software architecture diagrams as D2 v0.7.1 source rendered with ELK to canonical SVG.
mem0-vercel-ai-sdk
Mem0 provider for Vercel AI SDK (@mem0/vercel-ai-provider). TRIGGER when: user mentions "vercel ai sdk", "@mem0/vercel-ai-provider", "createMem0", "retrieveMemories", "addMemories", "getMemories", "searchMemories", "mem0 vercel", "AI SDK provider", "AI SDK memory", or is using generateText/streamText with mem0. Also…
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…