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/strvcom/flutter-template/spec-featurenpx skills add strvcom/flutter-template --skill spec-featuregit clone --depth 1 https://github.com/strvcom/flutter-templateWhat 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.00071 | $0.01209 |
| Opus 5 | $0.00036 | $0.00605 |
| Sonnet 5 | $0.00014 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade A, and why
spec-feature 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Spec Feature
Single entry point that runs the full feature specification pipeline from idea to implementation-ready tasks. It is designed to be invoked once; each sub-skill may pause for user input during its mandatory clarification steps — that is intentional and correct. After each sub-skill finishes, this orchestrator automatically invokes the next phase without requiring the user to type the next command.
Use this when you want to go from a feature idea directly to a full task breakdown, without
manually running /prd, /techspec, and /tasks in sequence.
Prerequisites
- No existing
prd.mdortechspec.mdfor this feature (or the user has confirmed it is safe to overwrite). - The user can answer clarification questions — both
prdandtechspechave mandatory interactive clarification steps that will pause the pipeline for user input.
If a PRD and tech spec already exist and are complete, use /start-job [feature-name] instead.
Arguments
Accepts an optional feature name. If provided, pass it to each sub-skill so they can pre-fill
the folder name and skip asking. If omitted, the prd sub-skill will determine the feature name
during its workflow.
Pipeline
Run each phase in order. Between phases, do NOT ask for user approval — the sub-skills themselves handle all necessary user interaction. If a phase fails hard (the sub-skill reports an unrecoverable error), stop and surface it to the user.
Critical orchestration rule: when a sub-skill returns control, do not treat its output as the end of your turn. You are still inside this
/spec-featureorchestrator. Immediately invoke the next phase's skill in the same response. The only valid stops are: (a) a sub-skill's mandatory clarification pause (which is correct — wait for the user, then resume), (b) a hard failure, or (c) the Final Report after Phase 3.
Phase 1 — Product Requirements Document
Invoke the prd skill (pass the feature name argument if provided).
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 · 108 lines · 71 tokens per session scan A 83379ae0e709
spec-feature is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,209 once invoked, about $0.0004 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
speckit-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
add-sample
Create a SamplesApp sample page with correct theming and attributes. Use when adding UI samples for controls.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…