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 eaglesakura/agent-skills --skill engineer-software-requirementgit clone --depth 1 https://github.com/eaglesakura/agent-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/eaglesakura/agent-skills/engineer-software-requirement)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/engineer-software-requirement"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/engineer-software-requirement.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.1 | $0.00152 | $0.01007 |
| Opus 5 | $0.00076 | $0.00504 |
| Sonnet 5 | $0.00030 | $0.00201 |
| Haiku 4.5 | $0.00015 | $0.00101 |
Grade A, and why
engineer-software-requirement 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 7d 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
エンジニア / 要件定義
主題は 何を満たせば完了か を曖昧さなく書くことである。
詳細設計（どう実装するか・差分）は engineer-software-design の役目であり、ここでは踏み込まない。
いつ使うか
- 機能・改修のゴール、前提、非機能、テスト観点が未整理のとき
/coding.requirementや Plan の要件フェーズ- 既存計画の「要件」だけを厚くしたいとき
詳細なコード差分・ファイルツリー・実装手順が欲しいときは本 SKILL ではなく engineer-software-design を使う。
アセットディレクトリ
../../assets/apm_modules/**/coding-xm3/.apm/assets/
入力
- ユーザーの依頼文、関連プロンプト、既存の計画ファイル（あればロード）
- 計画ファイルの置き場は
workspace-agent-temporary（.ai-agent/plan/）に従う
依頼が一言でも、完了条件・前提・テスト・影響範囲に分解してよい。足りない情報は推測で埋めず、不明点として残す。
ガードレール
- プロダクションコードは変更しない（計画ファイルとレビュー用 Markdown のみ更新してよい）
- 実装方針の断定や具体コード差分は書かない（必要なら「詳細設計で扱う」と残す）
実行手順
ステップ1. フォーマット確認
{assets}/coding/requirements.md（要件定義フォーマット）をロードする
ステップ2. 要件整理
与えられた情報から、少なくとも次を洗い出す。
- 完了条件（何ができていればタスク完了か）
- 前提条件・制約
- テスト観点（正常／異常／境界）
- 影響範囲（画面・API・データ・既存挙動）
- 暗黙的になりがちな要件（エラー表示、未ログイン、空データ、ローカライズ等）
ステップ3. 不明点の明示
- 不足・曖昧な点は推測で確定せず、会話として質問する／ドキュメントに「未決」として残す
- ユーザーが即答できない事項は、仮置きせず未決のままにして詳細設計へ渡さない（または未決リストを明示する）
ステップ4. 出力
{assets}/coding/requirements.md（要件定義フォーマット）に沿って出力する- 計画ファイルへ書く場合は
.ai-agent/plan/{計画名}.md（workspace-agent-temporary） - 必須セクションの目安: 要件カテゴリ、暗黙的な要件（なければ「なし」）、テスト要件
品質の目安
後続の詳細設計が「方針に従って実装」ではなく、受け入れ条件から差分を起こせる粒度であること。
職能の物差しが必要なときは agent-job-description を参照する（要件自体はジュニア向け疑似コードまでは落とさない）。
What ships with it
1 file 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.
- 7d ago First seen · 69 lines · 152 tokens per session scan A 24f38d76fc58
engineer-software-requirement is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed yesterday), licensed MIT. It adds 152 tokens to every session and 1,007 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…