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 Intai/story-flow --skill learn-technical-designgit clone --depth 1 https://github.com/Intai/story-flowWrote 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/intai/story-flow/learn-technical-design)<a href="https://agentmods.dev/skills/intai/story-flow/learn-technical-design"><img src="https://agentmods.dev/badge/skills/intai/story-flow/learn-technical-design.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00025 | $0.01682 |
| Opus 5 | $0.00013 | $0.00841 |
| Sonnet 5 | $0.00005 | $0.00336 |
| Haiku 4.5 | $0.00003 | $0.00168 |
Grade A, and why
Learn why to discuss technical design before implementation 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Why Discuss Technical Design Before Implementation?
Overview
This learning module helps junior developers understand why creating a technical design PR before implementation leads to better outcomes, faster delivery, and reduced rework.
Instructions
Present the following content interactively. After each section, use AskUserQuestion to offer 3 options:
- "Continue to next section"
- "Show me an example"
- "I have a question"
Section 1: The Purpose of Technical Design PRs
Explain that in story-flow, before writing implementation code, developers create a pull request containing their technical design:
A technical design PR serves three purposes:
- Early feedback on approach - Get team input before investing time in implementation
- Alignment before coding - Ensure everyone agrees on the direction
- Living documentation - The merged design becomes part of the repo history
The key insight:
A technical design PR is not about seeking permission. It's about leveraging collective expertise to find the best solution before committing to an approach.
What gets included:
- Story requirements (from the story tracker, Figma analysis)
- Planned tasks with execution order
- Pseudo code, example payloads, or expected API responses
- Questions or concerns for reviewers
Section 2: The Shift-Left Concept
Explain the "shift-left" principle:
Shift-left means moving quality activities earlier in the development lifecycle.
Traditional approach (problems found late):
Design → Code → Code Review → QA → Production
↑
Problems found here
(expensive to fix)
Shift-left approach (problems found early):
Design Review → Code → Code Review → QA → Production
↑
Problems found here
(cheap to fix)
Why "left"?
If you imagine the development timeline flowing left-to-right, shifting activities to the left means doing them earlier.
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 · 293 lines · 25 tokens per session scan A d15526b5e730
Learn why to discuss technical design before implementation is a skill published in the GitHub repository Intai/story-flow (12 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 1,682 once invoked, about $0.0001 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
automation
Instructions for managing scheduled tasks through the host's structured automation tool, including reminders, delayed work, recurring checks, and result delivery.
find-leads
Find qualified B2B leads with OpenOutreach — run openoutreach find N [emails], read the CSV it prints on stdout, and hand the rows to whatever sends. Use when the user wants leads, prospects, an ICP-matched contact list, or asks what a campaign already has. Also covers first-run setup (openoutreach init), openoutreach…
flame-harness-evaluator
Phase 6 — skeptical QA. Run the game, watch it, then judge against the contract. Default = functional check; --strict adds quality and edge-case passes.
flame-harness-design
Phase 3 — define the Flutter designtokens.dart spec (palette, typography, spacing), the game's art/visual concept, and the asset/audio sourcing plan.
flame-harness-screenshot
Phase 9 — capture store screenshots in the game's configured locales via integrationtest (ads hidden), fill ASO keywords, and upload via fastlane.
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.