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 tranfu-labs/tranfu-skills --skill strategy-first-developmentgit clone --depth 1 https://github.com/tranfu-labs/tranfu-skillsWrote 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/tranfu-labs/tranfu-skills/strategy-first-development)<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/strategy-first-development"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/strategy-first-development/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/tranfu-labs/tranfu-skills/strategy-first-development"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/strategy-first-development.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.00162 | $0.06344 |
| Opus 5.5 | $0.00065 | $0.02538 |
| Sonnet 5.5 | $0.00032 | $0.01269 |
| Haiku 4.5 | $0.00016 | $0.00634 |
Grade A, and why
strategy-first-development 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 1mo 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy First Development
Turn a vague or high-impact product/engineering request into a shared control plane before coding. Prevent arbitrary stacks, one-off UI, duplicate infrastructure, and custom engines chosen from memory instead of evidence.
This skill is a development workflow, not a skill-creation or prompt-review workflow. For skill creation, skill review, prompt review, or agent-definition review, route to the relevant skill-specific workflow instead.
Core Contract
CRITICAL: Complete strategic consensus, reference-project research, and the applicable technology-selection gate before presenting a stack as settled or starting implementation.
When technology selection is in scope, MUST read Technology Selection Protocol completely and run its SELECT_STACK procedure. Mature-product research and per-capability library selection are separate evidence layers; completing one does not satisfy the other.
Only materialize-strategy and the strategy phase of plan-then-implement may create or update the default artifacts:
AGENTS.md, docs/product/strategy.md, docs/product/north-star.md, docs/architecture/technical-stack.md, and docs/product/roadmap.md.
discuss-only and strategy-packet MUST NOT write files. All modes may surface assumptions, gaps, and provisional decisions.
CRITICAL: Strategy artifact materialization may create or update documentation artifacts only. It MUST NOT modify production app code, install dependencies, scaffold runtime modules, change deployment files, run destructive operations, or claim implementation completion unless a later implementation gate is explicitly passed.
For user-facing products, MUST define the project-specific AI/agent role and user-visible experience. Shipped UI MUST NOT expose planning notes, prompts, chain-of-thought, provider/model names, debug text, TODOs, or implementation workflow labels unless the product is explicitly a developer or observability tool.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 500 lines · 162 tokens per session scan A 72d19fca637a
strategy-first-development is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed 24d ago), licensed MIT. It adds 162 tokens to every session and 6,344 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.