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 instructions/careerchain-ys/stdd/agents-mdgit clone --depth 1 https://github.com/careerchain-ys/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/instructions/careerchain-ys/stdd/agents-md)<a href="https://agentmods.dev/instructions/careerchain-ys/stdd/agents-md"><img src="https://agentmods.dev/badge/instructions/careerchain-ys/stdd/agents-md.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 | $0.02708 | $0.02708 |
| Opus 5 | $0.01354 | $0.01354 |
| Sonnet 5 | $0.00542 | $0.00542 |
| Haiku 4.5 | $0.00271 | $0.00271 |
Grade A, and why
stdd AGENTS.md 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
このファイルは agents.md 標準に準拠した、AI エージェント向けのプロジェクト情報です。Claude Code をはじめとする AI エージェントは、リポジトリ作業を始める前にまず本ファイルを参照してください。
プロジェクト概要
STDD (Spec and Test Driven Development) は、AI エージェントと人間の開発者が協働し、仕様駆動・テスト駆動で開発を進めるための方法論・テンプレート・skill / agent 群を提供する OSS プロジェクトです。
- 対象: あらゆる Web アプリケーションプロジェクト
- 想定読者: stdd を導入する外部開発者 / プラグイン開発者 / リポジトリメンテナ / AI エージェント
- 言語: ドキュメントは日本語。英訳は将来検討
- ライセンス: Apache License 2.0
エージェントが最初に読むべき参考資料:
README.md— リポジトリの全体像packages/core/docs/stdd-methodology.md— STDD 方法論（開発フロー図を含む）docs/plugin-separation-policy.md— プラグイン分離方針
セットアップ手順
リポジトリをクローン直後にエージェントが実行すべきセットアップは以下です。
# 1. リポジトリを取得
git clone https://github.com/careerchain-ys/stdd.git
cd stdd
# 2. JSON Schema 検証ツールを取得（ローカル検証で使用、任意）
npx -y ajv-cli@5 compile --spec=draft2020 -s packages/core/schema/.stdd.config.schema.json
# 3. プラグイン構造を確認
ls plugins/
stdd 本体には Node.js / TypeScript のランタイム実装は含まれていません（v0.1.0 時点ではドキュメント・テンプレート・skill / agent 定義のみ）。npm install 等は不要です。
下流プロジェクトに stdd を組み込む場合は、README.md の Quick Start に従って .stdd.config.yml を作成してください。
ビルド・テスト・lint コマンド
stdd 本体はランタイムコードを含まないため、伝統的なビルド・テスト・lint コマンドは存在しません。代わりに以下の 検証コマンド を提供します。
| 目的 | コマンド |
|---|---|
| JSON Schema の構文検証 | npx -y ajv-cli@5 compile --spec=draft2020 -s packages/core/schema/.stdd.config.schema.json |
.stdd.config.yml の妥当性検証 |
YAML を JSON に変換してから ajv-cli validate で検証する。詳細手順は packages/core/README.md の「JSON Schema のローカル検証」セクション（js-yaml を介した変換例を含む）を参照 |
| プラグインメタデータの構文検証 | for f in plugins/*/plugin.json; do python3 -m json.tool "$f" > /dev/null && echo "OK $f"; done |
| 禁止語監査 | リポジトリの公開状態に応じて、旧名称・固有名詞が残っていないかを grep -rI で確認 |
| トレーサビリティ監査スクリプトの検証 | bash test/trace-audit.test.sh（packages/core/hooks/trace-audit.sh の順方向 gap 検知・逆方向影響範囲の振る舞いテスト） |
| 生成物のドリフト検査 | npm run check:adapters（.claude/ .agents/ .codex/ が packages/core/ と一致するか検査） |
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.
- 4d ago First seen · 134 lines · 2,708 tokens per session scan A db80bc82ebd5
stdd AGENTS.md is an instructions file published in the GitHub repository careerchain-ys/stdd (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,708 tokens to every session, about $0.0135 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.