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/start-jobnpx skills add strvcom/flutter-template --skill start-jobgit 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.00078 | $0.01138 |
| Opus 5 | $0.00039 | $0.00569 |
| Sonnet 5 | $0.00016 | $0.00228 |
| Haiku 4.5 | $0.00008 | $0.00114 |
Grade A, and why
start-job 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Start Job
Single entry point that runs the post-spec Flutter implementation pipeline. It is designed to be invoked once, with no user input between phases, so the feature goes from "spec approved" to "verified, uncommitted implementation" in one shot.
Use this only after the PRD and tech spec are finished. If another agent or developer is still editing the tech spec, do not start implementation yet.
Prerequisites
- PRD exists at
.claude/tasks/[feature-name]/prd.md - Tech Spec exists at
.claude/tasks/[feature-name]/techspec.md - The tech spec is complete and no other agent is actively editing it.
- The current working tree does not contain unresolved conflicts in
.claude/tasks/[feature-name]/.
If the PRD or techspec is missing, stop and ask the user to run /prd and/or /techspec
first. If the tech spec appears to be in progress, stop and ask the user to confirm it is ready.
Pipeline
Run each phase in order. Do NOT ask for user approval between phases. Do NOT commit anything at any point. If a phase fails hard (cannot proceed), stop and surface 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
/start-joborchestrator. Immediately invoke the next phase's skill in the same response. Do not stop, do not summarize, do not pause for user input between phases. The only valid stops are: (a) hard failure, (b) the Final Report after Phase 4.
Phase 1 — Task Breakdown
Invoke the tasks skill. It generates tasks.md and individual task files under
.claude/tasks/[feature-name]/. No approval prompt.
After tasks returns: do not stop, do not wait for input, do not summarize. Immediately
invoke implement-tasks-sequence (Phase 2) in the same response.
Phase 2 — Implementation
Invoke the implement-tasks-sequence skill. It executes all generated tasks in dependency
order, parallelizing when safe. No per-task builds, tests, or commits — agents only write
code changes.
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 · 93 lines · 78 tokens per session scan A 91621ef7e7b5
start-job is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 1,138 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.