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-deliverygit 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-delivery)<a href="https://agentmods.dev/skills/ymm-oss/fsl/fsl-delivery"><img src="https://agentmods.dev/badge/skills/ymm-oss/fsl/fsl-delivery.svg" alt="Measured on agentmods" height="20"></a>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.00107 | $0.02018 |
| Opus 5 | $0.00053 | $0.01009 |
| Sonnet 5 | $0.00021 | $0.00404 |
| Haiku 4.5 | $0.00011 | $0.00202 |
Grade A, and why
fsl-delivery 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 2d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FSL Delivery
Overview
Use this skill as the lifecycle coordinator for FSL-based delivery. It does not replace the layer-specific skills; it routes work to them, preserves the layer boundaries, and keeps proof, refinement, and implementation-conformance claims separate.
FSL is the checkable contract spine, not the entire product process — but that spine is broad by default: a spec replaces the prose business/requirements/design doc you would write anyway, so wide coverage across those layers needs no per-feature verification-ROI case. Natural language discovery, UI/API design, coding, and testing still happen in their normal tools; FSL supplies the machine-checkable contracts and counterexamples that constrain those artifacts.
The resulting spec corpus is the project's living single source of truth: each
layer is re-verified on every change (regression, drift, and cross-layer
change-impact via refine), and it doubles as onboarding context for humans and AI
approaching the flow it documents.
Routing
Before authoring a layer, read and follow the corresponding skill:
- Business process, As-Is/To-Be, controls, KPIs, goals:
../fsl-business/SKILL.md - PM/PdM requirements, acceptance criteria, forbidden flows, NFR/SLA:
../fsl-requirements/SKILL.md - Engineering design, internal state/actions, refinement mapping, testgen/replay
handoff:
../fsl-design/SKILL.md - Design review, variants, substitutability, SOLID/LSP/OCP judgment:
../fsl-design-review/SKILL.md - Cross-cutting dialect concerns — DB migration compatibility (
dbsystem,fslc db), Functional DDD / async effects (domain,fslc domain), AI tool-boundary and agent contracts plus statistical evidence (ai_component/agent,fslc ai):../fsl/references/advanced.md. These sit outside the business→requirements→design progression and are not stage-gated by this skill. - Syntax, verifier commands, JSON repair protocol:
../fsl/SKILL.md, then its topic-specific references as needed
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +6 lines 1433d6457864
- 7d ago First seen · 163 lines · 107 tokens per session scan A 6e482c305752
fsl-delivery is a skill published in the GitHub repository ymm-oss/fsl (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 107 tokens to every session and 2,018 once invoked, about $0.0005 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
wrap-up
Use ONLY when the user's latest message explicitly contains the /wrap-up command. Harvests everything a long session produced into the project following that project's own rules — moves stray media in, wires two-way refs, updates indexes, merges drafts into SSOT — then dispatches a context-free sub-agent to blind-test…
skill-cron
Use when the user wants to register, inspect, manually run, or remove scheduled Claude skills with Telegram push notifications. Presents a menu, discovers schedulable skills with headless-prompt frontmatter, converts natural-language schedules into cron entries with conflict confirmation, writes managed config, and…
kalender
Calendar skill with user-adaptive backend selection (Flag 3). Default: local SQLite store. Optional: Google Calendar MCP, Routinika or UpToday as backend — controlled via assist/prefs.json. Without preference the LLM asks the user interactively.
bewerbungsexperte
Spezialist fuer den gesamten Bewerbungsprozess. Analysiert Stellenanzeigen, optimiert Profile (LinkedIn/CV) und generiert massgeschneiderte Anschreiben. Generiert ASCII-Lebenslaeufe aus einer SQLite-Datenbank und Ordnerstruktur. cvgenerator.py ist standalone portiert -- keine BACH-Runtime noetig.