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/s977043/plangate/feature-implementnpx skills add s977043/PlanGate --skill feature-implementgit clone --depth 1 https://github.com/s977043/PlanGateWrote 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/s977043/plangate/feature-implement)<a href="https://agentmods.dev/skills/s977043/plangate/feature-implement"><img src="https://agentmods.dev/badge/skills/s977043/plangate/feature-implement.svg" alt="Measured on agentmods" 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 | $0.00075 | $0.00403 |
| Opus 5 | $0.00037 | $0.00201 |
| Sonnet 5 | $0.00015 | $0.00081 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
feature-implement 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 3d 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.
What it actually says
Feature Implement
design artifact に従って、機能を最小単位で実装する Skill。差分ごとに自己レビューと明示的な既知課題の記録を行う。
カテゴリ
Build
想定 Phase
WF-04 Build & Refine
入力
- design artifact（WF-03 出力）
- テスト観点（design 内で指定されたもの）
- 既存コードベース
出力
known-issues artifact + コード差分:
- 動作するコード（テスト付き）
- 自己レビュー結果
- 明示的な既知課題（妥協点 / 未着手項目）
- 実装単位ごとのコミット履歴
使い方
- WF-04 で implementation-agent が呼び出す
- TDD サイクル（RED → GREEN → REFACTOR）を最小単位で回す
- 出力は WF-05 の入力となる
関連
- Workflow:
docs/workflows/04_build_and_refine.md（配布対象外。install.sh --claude/ plugin / Codex の 3 経路とも導入先には配置されない。解決できない場合は本 Skill の記述を代替正本とし、「正本<path>を参照できなかった」と明示する） - Rule: Rule 2
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.
- 3d ago First seen · 43 lines · 75 tokens per session scan A 5ee87e475015
feature-implement is a skill published in the GitHub repository s977043/PlanGate (2 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 403 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-31.
Other skills, from other repositories
skill-maintenance
Automated skill maintenance tool (v6 — Unified Registry + Snapshots). Full scan: [Orphan] migrate misplaced skills from category dirs OR standalone skills/<name>/ to auto-generated/, [Sync] auto-generated/ vs registry lifecycle diff (new/deleted/revived + description auto-sync via lifecycle field), [Reg]…
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
marshal
Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.
wiki
Markdown-first knowledge base where the LLM acts as librarian. Ingests raw sources, compiles and interlinks topic files, self-maintains an index. No vector DB or embeddings required -- uses LLM-native navigation over structured markdown up to 400K words.