Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/careerchain-ys/stddnpx agentmods add skills/careerchain-ys/stdd/documenting-tech-specsWrote 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/careerchain-ys/stdd/documenting-tech-specs)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/documenting-tech-specs"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/documenting-tech-specs.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.00107 | $0.04193 |
| Opus 5 | $0.00053 | $0.02096 |
| Sonnet 5 | $0.00021 | $0.00839 |
| Haiku 4.5 | $0.00011 | $0.00419 |
Grade A, and why
documenting-tech-specs 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 6d 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
技術 spec (tech_specs) — TECH_DESIGN / TEST_PLAN / common 技術階層の作成
STDD（Spec and Test Driven Development）方法論に従って、技術系の設計書（総称 技術 spec / tech_specs）を作成・更新します。対象は feature の TECH_DESIGN.md・TEST_PLAN.md と、common 階層の ARCHITECTURE.md / TABLE_DEFINITION.md / API_SPEC.md / DESIGN.md（→ stdd-methodology.md §3）。
前提: 技術設計は REQUIREMENTS.md（要件）が確定していることを前提とする。要件（業務・機能・非機能）の作成は documenting-requirements Skill を使う。SSOT原則・要確認マーカーのSSoTも documenting-requirements にあるため、本スキルでもそれに従う（後述「絶対ルール」参照）。
Quick Start
新機能の技術設計を作成する場合
REQUIREMENTS.md（要件）が確定している前提で:
-
TECH_DESIGN.md を作成
docs/<app>/<path>/TECH_DESIGN.md- 章構成: 概要 / 主要な設計判断（任意）/ 画面項目定義（画面 feature は必須）/ ロジック設計（コア）/ エラーハンドリング戦略 / 非機能要件（任意）
- データ構造は common の
TABLE_DEFINITION.md、API は common のAPI_SPEC.mdを参照（再定義しない） - テンプレート を参照
-
TEST_PLAN.md を作成
docs/<app>/<path>/TEST_PLAN.md- テスト戦略（REQUIREMENTS のユースケース＋ TECH_DESIGN のロジック設計を E2E/Integration/Unit にマッピング）
- トレーサビリティ ID を貫通: TECH_DESIGN §1.1 対応表に要件ID（
UC-<feature>-NN）列、§4.2 その他処理フローにFL-<feature>-NN、TEST_PLAN に対象ID 列を持たせ、REQUIREMENTS §2.1 の**ID**:行と一致させる（抜け漏れはbash .claude/hooks/trace-audit.shで機械検知） - テンプレート を参照
横断要素（テーブル定義・API 仕様）は common 階層に集約する。新規テーブル / API が生じたら common の
TABLE_DEFINITION.md/API_SPEC.mdを更新し、feature からは参照する。
common 階層の技術ドキュメントを作成する場合
docs/common/ARCHITECTURE.md / TABLE_DEFINITION.md / API_SPEC.md / DESIGN.md
What ships with it
7 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.
- 6d ago First seen · 217 lines · 107 tokens per session scan A e761137797f9
documenting-tech-specs is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 107 tokens to every session and 4,193 once invoked, about $0.0005 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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…