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/morodomi/dev-crew/skills-kickoffnpx skills add morodomi/dev-crew --skill skills-kickoffgit clone --depth 1 https://github.com/morodomi/dev-crewWrote 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/morodomi/dev-crew/skills-kickoff)<a href="https://agentmods.dev/skills/morodomi/dev-crew/skills-kickoff"><img src="https://agentmods.dev/badge/skills/morodomi/dev-crew/skills-kickoff.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.00051 | $0.00779 |
| Opus 5 | $0.00026 | $0.00390 |
| Sonnet 5 | $0.00010 | $0.00156 |
| Haiku 4.5 | $0.00005 | $0.00078 |
Grade A, and why
kickoff 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 5d 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.
What it actually says
Progress Checklist
KICKOFF Progress:
- [ ] planファイル読み取り → 情報抽出
- [ ] Cycle doc生成（テンプレートから）
- [ ] Test List・設計情報の転記
- [ ] 完了メッセージ表示
禁止事項
- planファイルの内容を変更しない（読み取りのみ）
- 実装コード作成（GREENで行う）
- テストコード作成（REDで行う）
Workflow
Step 1: Read Plan File
plan modeで作成・承認されたplanファイルを読み取り、以下の情報を抽出:
- TDD Context: feature name, environment, scope, risk
- 探索結果: 既存パターン、影響範囲
- 設計方針: アーキテクチャ、依存関係
- Test List: 正常系/境界値/エッジケース/異常系
- QAチェック結果: カバレッジ・粒度・セキュリティ・独立性
Step 2: Generate Cycle Doc
Feature nameからファイル名を生成し、templates/cycle.md からCycle docを作成。
mkdir -p docs/cycles && NOW=$(date '+%Y-%m-%d %H:%M')
$NOW をfrontmatter (created/updated) とProgress Logに使用。Claude Codeは時刻を持たないため date 実行が必須。
planファイルから以下をCycle docに転記:
| Cycle doc セクション | planファイルからの転記元 |
|---|---|
| Scope Definition | In Scope / Out of Scope / Files to Change |
| Environment | Layer, Plugin, Risk, Runtime, Dependencies |
| Risk Interview | BLOCK時のインタビュー回答 |
| Context & Dependencies | 依存関係・参照ドキュメント |
| Implementation Notes | Goal, Background, Design Approach |
Step 3: Transfer Test List
planファイルのTest ListをCycle docのTest Listセクションに転記。
## Test List
### TODO
- [ ] TC-01: [test case]
- [ ] TC-02: [test case]
### WIP
(none)
### DISCOVERED
(none)
### DONE
(none)
Step 3.5: Codex Debate (optional)
which codexでCodex利用可能か確認- 利用不可 → 既存 review --plan にフォールバック（結果をProgress Logに記録）、Step 4へ
- 利用可能 → reference.mdのDebate Workflowを実行
- 結果をCycle docのImplementation Notesに追記（Accepted/Rejected/Deferred）
Step 4: Complete
Output: KICKOFF完了。Cycle doc: {path}。次: orchestrate→自動RED / 手動→ /review --plan
Reference
- reference.md / Templates: ../spec/templates/cycle.md
What ships with it
2 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.
- 5d ago First seen · 89 lines · 51 tokens per session scan A 5f1a7d325100
kickoff is a skill published in the GitHub repository morodomi/dev-crew (1 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 779 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-31.
Other skills, from other repositories
testing-principles
Language-agnostic testing principles including TDD, test quality, coverage standards, and test design patterns. Use when writing tests, designing test strategies, or reviewing test quality.
tdd
This skill should be used when the user asks to "add a feature using TDD", "fix a bug with TDD", "do TDD", "red-green-refactor", "write a failing test first", "use test-driven development", "start TDD", "test first approach", "TDD loop", "TDD cycle", or mentions TDD workflow, baby steps, guessing game, or…
unfolding-orchestrator
Orchestrator role in the Unfolding Specs process. Launches the PO, forwards unsolicited Sensei guidance, handles genuine commissioner issues, and resumes the workflow through the platform-specific live task mechanism.
github-safety
This skill should be used when working on any project hosted on GitHub. It provides prompt-injection defense rules for GitHub issues and pull requests. Always-on security rules plus optional workflow conventions.
ci-cd
Use when working on CI/CD pipelines and automation — build, test, and deploy automation, pipeline design, and deployment strategies. Triggers on "CI pipeline", "GitHub Actions", "deployment strategy", "CI/CD", "流水线", "持续集成", "部署策略".
release-notes
Generate and publish concise, evidence-based notes in the body of the latest existing GitHub Release. Use only when the user explicitly invokes $release-notes or explicitly asks to update the latest existing GitHub Release body. Do not invoke for general release planning, changelog, tag, or version tasks.