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/techspecnpx skills add strvcom/flutter-template --skill techspecgit 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.00064 | $0.01473 |
| Opus 5 | $0.00032 | $0.00737 |
| Sonnet 5 | $0.00013 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00147 |
Grade A, and why
techspec 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Specification
You are a technical specification expert translating PRDs into implementation-ready specs for
this Flutter app. The stack is flutter_riverpod + riverpod_annotation for state, freezed
json_serializablefor data classes,auto_routefor navigation,diofor HTTP, Firebase services for backend, and FVM-pinned Flutter SDK.
Objectives
- Translate the PRD into concrete technical guidance grounded in this codebase
- Reuse existing patterns from
lib/features/<feature>/and primitives fromlib/common/before proposing new ones - Specify the data → state → UI → integration build order so the
tasksskill can break it into ordered work units
Prerequisites
- Required:
.claude/tasks/[feature-name]/prd.md - Output:
.claude/tasks/[feature-name]/techspec.md
Workflow
Step 0: Load Shared Context
Before reading the PRD, check whether .claude/tasks/[feature-name]/context.md exists. If it
does, read it. Use its contents to skip re-deriving already-captured decisions (problem
statement, target platforms, key product decisions, out-of-scope items) — do not ask the user
about things already settled there.
Step 1: Analyze PRD
Read the PRD at .claude/tasks/[feature-name]/prd.md and extract:
- Core requirements and constraints
- Domain entities involved (data shapes, sources, lifetimes)
- Platform scope — which of Android / iOS / web / desktop are in scope, and whether any platform-specific behaviors apply
- Whether the feature touches Firebase services, native channels, or other integrations
Step 2: Deep Project Analysis
Explore the codebase to ground the spec in reality:
- Look for existing features under
lib/features/that follow a similar shape and should be mirrored (the canonical pattern is*_page.dart+*_page_content.dart+*_state.dart+*_event.dart). - Check
lib/common/for reusable widgets, extensions, theming, formatters before introducing new primitives. - Inspect existing DTOs (
lib/common/data/dto/), entities (lib/common/data/entity/), use cases, and providers for naming / mapping conventions. Add a repository layer only if the project already has one for this area or the spec explicitly justifies it. - Check
lib/app/setup/setup_app.dartto see which services / integrations are actually active versus scaffolded. - Read
AGENTS.md,docs/PROJECT_OVERVIEW.md, anddocs/PROJECT_GUIDELINES.mdfor the canonical conventions.
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 · 139 lines · 64 tokens per session scan A 1e38ee140f62
techspec is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,473 once invoked, about $0.0003 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
planning-with-files-ar
تخطيط مستمر قائم على الملفات لعمل وكلاء الذكاء الاصطناعي متعدد الخطوات. يحتفظ بملفات taskplan.md و findings.md و progress.md على القرص، وتحقن خطافات دورة الحياة سياق التخطيط المحدد للمشروع. تقرأ الاستعادة التلقائية ملفات تخطيط المشروع فقط. يمكن للأمر الصريح session-catchup.py --metadata فحص بيانات وصفية لجلسات الوكيل…
kl-consistency-test
Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths computing the same function), which helper separates them, how to pick a threshold once they hold, and how to localize a…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
dsh-web-documentation
Use when adding or editing dsh-web README files, docs, AGENTS.md instructions, user-facing configuration text, or bilingual documentation pairs.
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
indication-dossier
Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.