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/implementnpx skills add strvcom/flutter-template --skill implementgit 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.00105 | $0.01637 |
| Opus 5 | $0.00053 | $0.00818 |
| Sonnet 5 | $0.00021 | $0.00327 |
| Haiku 4.5 | $0.00011 | $0.00164 |
Grade A, and why
implement 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Task Implementation
You are responsible for implementing one task from a Flutter feature plan while following the repository standards.
Objectives
- Read and understand the task definition
- Review the PRD and tech spec for context
- Apply relevant Flutter skills and repository conventions
- Execute the implementation
- Verify the change when running standalone, or explicitly skip verification when called by
implement-tasks-sequence
File Locations
- PRD:
.claude/tasks/[feature-name]/prd.md - Tech Spec:
.claude/tasks/[feature-name]/techspec.md - Task:
.claude/tasks/[feature-name]/[num]_task.md - Task list:
.claude/tasks/[feature-name]/tasks.md
Applicable Skills
feature-screen— when the task adds or changes a screen, route, page split, UI state, or navigation.feature-data-flow— when the task adds backend/storage data flow, DTOs, entities, use cases, or state that loads real data.widget-test— when the task changes shared UI, provider-driven visual states, or user-visible behavior that can be covered by a focused widget test.layout-debug— when the task involves overflow fixes, responsive behavior, scroll/constraint issues, or text clipping.lint-format— when running standalone and the change does not need the broaderbuild-verifysuite.build-verify— when running standalone and the task changed behavior, generated-code inputs, routes, platform setup, dependencies, tests, or other shared behavior.pr-review— optional standalone final check when the user asks for a review after implementation.
Do not use KMP, Swift, iOS coordinator, Gradle, Spotless, Detekt, Tuist, or native iOS test-runner skills in this Flutter workflow.
Invocation Modes
Standalone mode
Use when the user directly asks to implement one task. Complete implementation and run the appropriate verification commands before reporting done.
Sequence mode
Use when called by implement-tasks-sequence. In this mode:
- read the same task, PRD, and tech spec
- write only the source changes for the assigned task
- do not run builds, tests,
lint-format,build-verify, orpr-review - do not commit or stage
- report what changed and return control to the orchestrator
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 · 128 lines · 105 tokens per session scan A 65b354ee0c3f
implement is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 105 tokens to every session and 1,637 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
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.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
app_remix
Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.