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/prdnpx skills add strvcom/flutter-template --skill prdgit 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.00077 | $0.01239 |
| Opus 5 | $0.00039 | $0.00620 |
| Sonnet 5 | $0.00015 | $0.00248 |
| Haiku 4.5 | $0.00008 | $0.00124 |
Grade A, and why
prd 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template PRD Creation
You are a PRD creation specialist focused on producing clear, actionable product requirements for this Flutter template.
Objectives
- Capture complete, clear, and testable requirements
- Separate product behavior from implementation design
- Capture Flutter-relevant product constraints such as target platforms, offline behavior, accessibility, localization, analytics, privacy, and integrations
- Generate a PRD using the standardized template
Template Reference
- Template:
.agents/templates/prd.md(also reachable as.claude/templates/prd.md) - Output:
.claude/tasks/[feature-name]/prd.md
Read First
AGENTS.mddocs/PROJECT_OVERVIEW.mddocs/PROJECT_GUIDELINES.md.agents/templates/prd.md- any user-provided brief, ticket, design, API notes, or KMP/source-platform reference material
Scope Boundary
A PRD describes what the feature should do and why it matters. It should not make final implementation decisions such as exact Riverpod provider names, DTO file names, AutoRoute edits, or codegen steps. Those belong in techspec.
It is still useful to capture high-level constraints that affect implementation, such as:
- target Flutter platforms: Android, iOS, web, macOS, Windows, Linux
- required backend, Firebase, notification, analytics, or native integrations
- offline or poor-connectivity expectations
- accessibility, text scaling, contrast, and localization requirements
- data sensitivity, consent, PII, storage, or security expectations
- KMP-to-Flutter migration parity requirements when the PRD is based on an existing source feature
Workflow
Step 1: Clarify (Mandatory)
Before writing anything, ask the user targeted questions about:
- The problem being solved and who it affects
- Core functionality and expected behavior
- Target platforms and any platform-specific behavior
- UX expectations, accessibility, and localization scope
- Backend/API/Firebase/notification/analytics dependencies
- Data sensitivity, privacy, and storage expectations
- Offline support, sync, loading, empty, and error states
- Migration parity if this is being converted from KMP or another source implementation
- Scope boundaries: what is explicitly out of scope
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 · 137 lines · 77 tokens per session scan A 343908a0b7ac
prd is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 1,239 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…