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 agentmods add skills/ymm-oss/fsl/task-startnpx skills add ymm-oss/fsl --skill task-startgit clone --depth 1 https://github.com/ymm-oss/fslWhat 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 | $0.00025 | $0.00265 |
| Opus 5 | $0.00013 | $0.00133 |
| Sonnet 5 | $0.00005 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
task-start 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.
What it actually says
Start an FSL task
Use this skill before substantial implementation, debugging, review, or design work.
- Inspect the current branch and
git status --short. - Restate the requested outcome as an observable goal and list explicit non-goals.
- Identify the authority surface: relevant contracts, design documents, tests, native Rust paths, and user constraints.
- Inspect only the narrow evidence needed to establish the current state. Delegate broad, read-heavy exploration to
evidence_explorerwhen it reduces the main context. - Create or replace
tasks/active.mdfromtasks/active.template.md. - Record invariants, evidence, scope, sibling paths, verification commands, remaining uncertainty, the discovered-follow-up ledger, and one concrete next action. For migration or parity work, inventory behavior-bearing AST/enum variants; top-level corpus counts are not semantic completeness.
- Remove stale or speculative content from a previous task.
- Stop before implementation so the task packet can be checked independently.
Keep the packet concise. Do not paste raw logs, full search results, secrets, or machine-specific absolute paths.
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 First seen · 22 lines · 25 tokens per session scan A eda8878bbbda
task-start is a skill published in the GitHub repository ymm-oss/fsl (21 stars, last pushed 5d ago), licensed Apache-2.0. It adds 25 tokens to every session and 265 once invoked, about $0.0001 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
propagate
Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires.
allium
Give your AI agents something more useful than a prompt. Velocity through clarity.
elicit
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help…
tend
Tend the Allium garden. Use when the user wants to write, edit, update, add to, improve, clarify, refine, restructure, fix or migrate Allium specs. Covers adding entities, rules, triggers, surfaces and contracts, fixing syntax or validation errors, renaming or refactoring within specs, migrating specs to a new…
weed
Weed the Allium garden. Find where Allium specifications and implementation code have diverged, and help resolve the divergences. Use when the user wants to check spec-code alignment, compare specs against implementation, audit for spec drift or violations, sync specs with code or code with specs, or verify whether…
witness
Independently witness that an Allium loop's convergence claim is true and was reached honestly. Use when the user wants to verify a loop's self-report, confirm tests really pass and no generated test was weakened, produce a convergence certificate or witness record, gate CI on a trustworthy signal, or check that an…