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/geekfujiwara/codeappsdevelopmentstandard/spec-buildernpx skills add geekfujiwara/CodeAppsDevelopmentStandard --skill spec-buildergit clone --depth 1 https://github.com/geekfujiwara/CodeAppsDevelopmentStandardWhat 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.00060 | $0.02882 |
| Opus 5 | $0.00030 | $0.01441 |
| Sonnet 5 | $0.00012 | $0.00576 |
| Haiku 4.5 | $0.00006 | $0.00288 |
Grade A, and why
spec-builder 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 2d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
仕様書作成スキル（一次情報 → 要件定義書）
office ドキュメント（PDF / PowerPoint / Excel / Word など）は anthropics/skills で読み取り、
画像ファイル（PNG/JPG 等）は agent-ocr で OCR する。
フォルダ構造
spec/ ← スキル専用ディレクトリ
├── input/ # ここに変換したいファイルを置く（ユーザーが操作）
├── output/ # 全出力はここに入る（ユーザーが参照）
│ ├── staging/ # ファイル単位の中間 markdown
│ └── docs/ # 統合要件定義書 5 点
│ ├── index.md # ドキュメント一覧・開発利用フロー
│ ├── business-requirements.md
│ ├── functional-requirements.md
│ ├── design-requirements.md
│ └── test-requirements.md
└── .cache/ # システム内部用（ユーザーは触らない）
├── conversion-checklist.json
├── pending_ocr.json
└── pending_skills.json
最初の依頼を簡単にする
このスキルは 引数なしでも開始できる。
- 既定入力:
spec/input/ - 既定 staging 出力:
spec/output/staging/ - 既定 docs 出力:
spec/output/docs/ - 既定 checklist:
spec/.cache/conversion-checklist.json --input/--staging/--docs（互換:--output）/--checklistを指定した場合はそのパスを優先するspec/input/に変換対象が見つからない場合、scripts/convert_documents.pyはワークスペース・フォルダ全体をスキャンし、変換候補になりうるファイルがないか確認する。候補が見つかった場合は一覧を提示するので、spec/input/へ移動するか--inputで対象パスを指定する- 「
spec/input/へ移動する」とは元の場所のファイルを削除するまでを含む。spec/input/へコピーしただけで元ファイルを残すと、ワークスペース上に同一内容のファイルが重複し混乱の元になる。コピー→取り込み確認後は元ファイルを削除すること
処理フロー
[spec/input/]
│
├─ 画像 (PNG/JPG 等) ──→ spec/.cache/pending_ocr.json ──→ agent-ocr
│ │
└─ 文書 (PDF/Office) ──→ spec/.cache/pending_skills.json ──→ anthropics/skills
│
┌─────────────┘
▼
[spec/output/staging/]
│
(Claude が統合)
│
[spec/output/docs/]
├── index.md
├── business-requirements.md
├── functional-requirements.md
├── design-requirements.md
└── test-requirements.md
What ships with it
4 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.
- 2d ago First seen · 190 lines · 60 tokens per session scan A d7939165b089
spec-builder is a skill published in the GitHub repository geekfujiwara/CodeAppsDevelopmentStandard (59 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 2,882 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.