Borrowing it
Nothing to install: this file belongs to ymm-oss/fsl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ymm-oss/fsl/main/.claude/skills/new-spec/SKILL.mdgit 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/new-spec)<a href="https://agentmods.dev/skills/ymm-oss/fsl/new-spec"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/new-spec/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/new-spec"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/new-spec.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 Agent Snooping · line 8 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00036 | $0.00296 |
| Opus 5.5 | $0.00014 | $0.00118 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
new-spec 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 2mo 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.
What it actually says
Author a meaningful FSL spec
Read skills/fsl/SKILL.md and only its relevant topical reference before writing syntax. Use the working-tree native prefix:
cargo run --manifest-path rust/Cargo.toml -p fslc-rust --bin fslc --
Gate
check <spec>for syntax and semantic diagnostics.verify <spec> --depth 8or a justified bound for bounded evidence.verify <spec> --engine inductionwhen the intended claim is unbounded.mutate <spec>to measure whether properties constrain behavior.verify <spec> --vacuity errorwhere applicable.- Run the focused corpus/command test required by the spec's dialect or example family.
Do not hollow out a spec to dodge a counterexample. Confirm source requirements and exceptions before inventing behavior. Keep confirmed assumptions with the spec using established metadata. If FSL is the wrong tool for the behavior, say so rather than forcing a vacuous model.
Changing a corpus file may affect contract or compatibility artifacts. Use their owning generator only after confirming the semantic change is intentional; never hand-edit a snapshot.
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.
- 2mo ago First seen · 29 lines · 36 tokens per session scan A 50e9c1c0e0e6
new-spec is a skill published in the GitHub repository ymm-oss/fsl (35 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 296 once invoked, about $0.0001 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
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
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…
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
mem0-remember
Stores a memory verbatim from user input with appropriate type classification and metadata. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a decision, preference, convention, or learning.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.