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/tailoring-spec-formatWrote 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/tailoring-spec-format)<a href="https://agentmods.dev/skills/careerchain-ys/stdd/tailoring-spec-format"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/tailoring-spec-format/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/careerchain-ys/stdd/tailoring-spec-format"><img src="https://agentmods.dev/badge/skills/careerchain-ys/stdd/tailoring-spec-format.svg" alt="Reviewed on agentmods" width="80" 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.00187 | $0.02145 |
| Opus 5.5 | $0.00075 | $0.00858 |
| Sonnet 5.5 | $0.00037 | $0.00429 |
| Haiku 4.5 | $0.00019 | $0.00215 |
Grade A, and why
tailoring-spec-format 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 2mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
spec フォーマットのテーラリング
STDD のテンプレートをこのプロジェクト固有に仕立て直す（テーラリング）。 STDD 導入（既存プロジェクト, step 3-4）・立ち上げ（新規プロジェクト, step 4）の 初期フォーマット策定 と、運用中の ブラッシュアップ（step 7）を担う。
導入/立ち上げフロー全体は
guide-for-existing-project.md/guide-for-new-project.md、 駆動役はintroducing-stdd（既存）/starting-new-with-stdd（新規）を参照。本スキルは単体でも呼べる。
設計方針（重要）
- フォーマットの決定そのものは人間（ビジネス・チーム判断）。本スキルはそれを促し・記録し・反映する手続きに徹する。
- agent オーケストレーションはしない。エージェントがメインセッションで決定ポイントを 1 つずつ提示し、人間に決めてもらう。
- 決定は 導入PLAN / 立ち上げPLAN の「フォーマット決定ログ」 に集約（SSOT）。spec 本体に経緯・履歴を書かない。
前提（素材）
- 初期:
docs/common/（common spec）と最初の feature spec 1 つが既にある（既存導入なら reverse、新規立ち上げなら順行で作成）。 - ブラッシュアップ: 既に複数の feature spec が運用されている。
手順
1. 素材レビュー
現状を把握する。
□ docs/common/REQUIREMENTS.md / ARCHITECTURE.md（common 階層の構成）
□ 代表 feature spec（REQUIREMENTS.md / TECH_DESIGN.md / TEST_PLAN.md）の実物
□ 現在の .stdd.config.yml（docs.layout / apps / commands）
□ 利用中のテンプレ（`.claude/skills/documenting-requirements/templates/`・`.claude/skills/documenting-tech-specs/templates/` または プロジェクト側コピー）
□ (step 7 のみ) 運用中の全 feature spec のばらつき・過不足
2. 決定ポイントを 1 つずつ提示（★人間が決める）
各項目について 現状 → 選択肢 → 推奨 を提示し、ユーザーに決めてもらう。一度に押し付けない。
| 決定ポイント | 論点 | 反映先 |
|---|---|---|
| spec ファイル構成 | feature 必須（要件 spec: REQUIREMENTS／技術 spec: TECH_DESIGN / TEST_PLAN）・任意（wireframes）と common（技術 spec: TABLE_DEFINITION / API_SPEC / DESIGN）をどう組むか | プロジェクトのテンプレ・運用ルール |
| common 固有セクション | common ARCHITECTURE に足す横断トピック（認証・認可 / RLS・権限 / 通知 / 監査ログ 等） | docs/common/ARCHITECTURE.md |
| docs.layout パス規約 | 単一/複数アプリ、feature_path の切り方、common の置き場 |
.stdd.config.yml の docs.layout |
| Priority 基準 | このプロジェクトでの P0/P1/P2 の具体定義（何を Critical とするか） | テンプレ注記 + 決定ログ |
| テスト層の責務分担 | E2E/Integration/Unit の線引き（既存テスト資産に合わせる） | TEST_PLAN テンプレのテスト戦略節 |
| 命名・用語 | プロジェクト固有語彙（アクター名・ドメイン用語）、テンプレのプレースホルダ実値化 | テンプレ・common spec |
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.
- 2mo ago First seen · 104 lines · 187 tokens per session scan A dc7b5a54e2ab
tailoring-spec-format is a skill published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 187 tokens to every session and 2,145 once invoked, about $0.0007 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…