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 u9401066/template-is-all-you-need --skill feature-developmentgit clone --depth 1 https://github.com/u9401066/template-is-all-you-needWrote 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/u9401066/template-is-all-you-need/feature-development)<a href="https://agentmods.dev/skills/u9401066/template-is-all-you-need/feature-development"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/feature-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/u9401066/template-is-all-you-need/feature-development"><img src="https://agentmods.dev/badge/skills/u9401066/template-is-all-you-need/feature-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.00064 | $0.01335 |
| Opus 5 | $0.00032 | $0.00668 |
| Sonnet 5 | $0.00013 | $0.00267 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
feature-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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- feature-development — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
功能開發工作流
描述
完整的功能開發流程，從規劃到部署，編排多個 Skills 協同工作。
觸發條件
- 「新功能開發」「implement feature」「建立新功能」
- 「FD: [功能名稱]」
📋 工作流程
┌─────────────────────────────────────────────────────────────┐
│ Feature Development Workflow │
├─────────────────────────────────────────────────────────────┤
│ Phase 1: 📐 規劃 (Planning) │
│ ├─ 需求分析與確認 │
│ ├─ 識別影響範圍 │
│ └─ 更新 Memory Bank (activeContext) │
├─────────────────────────────────────────────────────────────┤
│ Phase 2: 🏗️ 架構 (Architecture) │
│ ├─ [ddd-architect] 生成 DDD 結構 │
│ ├─ 建立介面定義 │
│ └─ 更新架構文檔 │
├─────────────────────────────────────────────────────────────┤
│ Phase 3: 🧪 測試先行 (TDD) │
│ ├─ [test-generator] 生成測試框架 │
│ ├─ 撰寫失敗的測試案例 │
│ └─ 定義驗收標準 │
├─────────────────────────────────────────────────────────────┤
│ Phase 4: 💻 實作 (Implementation) │
│ ├─ 實作 Domain 層 │
│ ├─ 實作 Application 層 │
│ ├─ 實作 Infrastructure 層 │
│ └─ 實作 Presentation 層 │
├─────────────────────────────────────────────────────────────┤
│ Phase 5: ✅ 驗證 (Verification) │
│ ├─ 執行測試套件 │
│ ├─ [code-reviewer] 程式碼審查 │
│ ├─ [security-reviewer] 安全檢查 │
│ └─ 靜態分析 (mypy, ruff, vulture) │
├─────────────────────────────────────────────────────────────┤
│ Phase 6: 📦 提交 (Commit) │
│ ├─ [memory-updater] 更新 Memory Bank │
│ ├─ [git-precommit] 執行提交前檢查 │
│ └─ 提交變更 │
└─────────────────────────────────────────────────────────────┘
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.
- 9d ago First seen · 160 lines · 0 tokens per session scan A e227f1dd4e3a
feature-development is a skill published in the GitHub repository u9401066/template-is-all-you-need (3 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 1,335 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-31.
Other skills, from other repositories
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
taskwarrior
Use when querying or modifying tasks via the taskwarrior CLI - dense recipes for listing, single-field lookups, multi-task batched lookups, full-text search, and the soft description-length convention. Activates on task list, task add, task info, task done, "what's on the backlog", "find a task", or any taskwarrior…
daily-working
End-to-end pipeline: pull a task from Redmine by ID, sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension (claude-in-chrome), and keep the Redmine ticket in sync throughout (in-progress…
grooming-sprint-tasks
Grooms sprint tasks by cross-referencing Monday.com board with GitHub issues across multiple repos, then produces subitems, descriptions, linked issues, and SP estimates. Use when grooming a sprint, planning sprint tasks, preparing for sprint planning, or when user says "groom", "sprint planning", "cross-reference…
acceptance-orchestrator
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
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…