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/introducing-stddWrote 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/introducing-stdd)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/introducing-stdd"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/introducing-stdd.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.00168 | $0.03149 |
| Opus 5 | $0.00084 | $0.01574 |
| Sonnet 5 | $0.00034 | $0.00630 |
| Haiku 4.5 | $0.00017 | $0.00315 |
Grade A, and why
introducing-stdd 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.
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STDD 導入ドライバー（既存プロジェクト）
既存プロジェクトへの STDD 導入を、セッションで 1 ステップずつ進めるための薄い駆動役。 自前の実装ロジックは持たず、各ステップで既存スキルを順に呼び、人間判断ポイントで停止し、進捗を導入PLANに記録する。
「なぜ」「各ステップで何を判断するか」は
guide-for-existing-project.mdを参照。 本スキルはその operational な実行役。
設計方針（重要）
- agent オーケストレーションはしない。エージェントがメインセッションで手順を進める軽量ドライバー。
- 導入は一度きり・判断主体のため、人間を常にループに入れる（フォーマット策定・優先順・粒度は必ず確認）。
- 状態は導入PLAN（
docs/common/plans/stdd-introduction.md）にのみ持つ。本スキルはステートレス。
起動時の動作
1. 導入PLAN の有無を確認
docs/common/plans/stdd-introduction.md
- 無い場合 → 初回: 下記「初回フロー」を実行し、導入PLAN を作成する。
- ある場合 → 再開: 導入PLAN を読み、最初の未チェック項目（
- [ ]）を「次にやること」として提示し、該当ステップを実行する。
2. 設定確認
.stdd.config.yml を読み、apps[] / docs.layout（common_requirements / common_architecture 含む）を把握する。無ければ step 0（対話的セットアップ） を実行する（下記「step 0」詳細）。
ステップ実行表
各ステップは「呼ぶスキル」と「停止して人間に確認すること」を持つ。
| step | 実行内容 | 呼ぶスキル | ★停止して確認 |
|---|---|---|---|
| 0 | .stdd.config.yml を対話的に作成（下記「step 0」詳細）/ テンプレ・skill 配置 |
— | 構成（単一/複数アプリ・パス規約） |
| 1 | common 階層生成 | reverse-engineering-common-spec |
生成後の要確認マーカー一覧 |
| 1.5 | 機能インベントリ + 優先順 → 導入PLAN へ記載 | — | ★ 機能一覧と優先順（P0 から） |
| 2 | 代表機能 1 つをリバース | reverse-engineering-feature-spec |
★ Spec 粒度・スコープ |
| 3-4 | フォーマット策定 → テンプレ特化 | tailoring-spec-format |
★★ フォーマット決定（テーラリング） |
| 5 | 残り機能を優先順でループ | reverse-engineering-feature-spec |
★ 機能ごとの粒度 |
| 6 | 順行運用へ移行 | auto-implement（以降） |
導入完了の確認 |
各機能リバース後は verifying-consistency で spec ⇔ test ⇔ 実装 の整合を確認する。
初回フロー（導入PLAN が無いとき）
- プロジェクト点検: ディレクトリ構成・
package.json・ルーティングをざっと把握。 - step 0（対話的セットアップ）:
.stdd.config.ymlが無ければ、下記「step 0」手順で 点検 → 草案 → 確認 → 書き込み を対話的に行う。 - step 1 実行:
reverse-engineering-common-specを呼び、common 階層を生成。要確認マーカー（仮説つき）を一覧化して人間に提示。 - step 1.5（★人間判断）: ルーティング・主要ドメインから機能を洗い出し、優先順をユーザーと合意。
- 導入PLAN 生成:
templates/introduction-plan.mdを雛形にdocs/common/plans/stdd-introduction.mdを作成し、機能を優先順で並べる。 - 「次は step 2（代表機能のリバース）」を提示して停止。
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 · 189 lines · 168 tokens per session scan A 2a2b4224f4fe
introducing-stdd is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 168 tokens to every session and 3,149 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
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.