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 makifbaysal/tasktrooper --skill native-vs-flutter-decisiongit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/native-vs-flutter-decision)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/native-vs-flutter-decision"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/native-vs-flutter-decision/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/native-vs-flutter-decision"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/native-vs-flutter-decision.svg" alt="Reviewed on agentmods" width="80" 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.00035 | $0.00590 |
| Opus 5.5 | $0.00014 | $0.00236 |
| Sonnet 5.5 | $0.00007 | $0.00118 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
native-vs-flutter-decision 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 8d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native vs Flutter Decision
Overview
Flutter is the default for cross-platform mobile; native (SwiftUI / Jetpack Compose) is chosen when a task needs deep platform integration or the app is already native. Decide at the start — you cannot half-migrate an app mid-task.
Core principle: The existing app's stack wins by default. Only greenfield apps or the analiz task's direction open the choice.
Decision
digraph m {
"App already single-stack?" [shape=diamond];
"Follow the app's stack" [shape=box];
"Needs deep platform integration?" [shape=diamond];
"Native (SwiftUI / Compose)" [shape=box];
"Flutter (default)" [shape=box];
"App already single-stack?" -> "Follow the app's stack" [label="yes"];
"App already single-stack?" -> "Needs deep platform integration?" [label="greenfield"];
"Needs deep platform integration?" -> "Native (SwiftUI / Compose)" [label="yes"];
"Needs deep platform integration?" -> "Flutter (default)" [label="no"];
}
Choose Flutter when
- Cross-platform (iOS + Android) from one codebase, standard UI + platform-channel-level device access.
- Greenfield app with no hard native requirement.
- The app is already Flutter — always.
Choose native when
- The task needs platform capabilities Flutter exposes poorly: advanced widgets/animations tied to the OS, deep HealthKit/CarPlay/WidgetKit, App Clips, live activities, tight ARKit/CameraX use.
- The app is already native (SwiftUI for iOS, Compose for Android) — always follow it.
- The analiz task specifies native.
Hard Rule
Never introduce a second UI stack into a single-stack app. A Flutter app that "needs one native screen" embeds it via a platform view (PlatformView/AndroidView/UiKitView) or talks to it through a MethodChannel/Pigeon — it does not gain a parallel SwiftUI module on your initiative. Going the other way (a native app needing a Flutter module) is Flutter add-to-app, not a rewrite. Flag genuine cross-stack needs in a task comment for the architect.
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.
- 8d ago First seen · 57 lines · 35 tokens per session scan A b899fcf847dc
native-vs-flutter-decision is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 590 once invoked, about $0.0001 per session on Opus 5.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-10-05.
Other skills, from other repositories
architecture-design
Use this skill to design system architecture with documented trade-offs and decisions before any implementation begins. Activates when a feature, system, or component requires non-trivial structural decisions about how components interact, what data stores to use, or how to decompose a problem.
repository-discovery
Use this skill to systematically explore an unfamiliar codebase before making any changes. Activates when starting work in an unknown repository, adding a new feature, debugging without prior context, or when no CONTEXT.md exists. Produces a grounded understanding of architecture, conventions, and constraints.
rapid-prototyping
Use this skill to build disposable, rapid proof-of-concept prototypes and spikes to test feasibility, validate API designs, or explore library capabilities before committing to a full production architecture.
ramp
Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
paperclip-task-bridge
Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.