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/stanshy/agenthub/project-kickoffnpx skills add Stanshy/AgentHub --skill project-kickoffgit clone --depth 1 https://github.com/Stanshy/AgentHubWrote 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/stanshy/agenthub/project-kickoff)<a href="https://agentmods.dev/skills/stanshy/agenthub/project-kickoff"><img src="https://agentmods.dev/badge/skills/stanshy/agenthub/project-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.00024 | $0.00929 |
| Opus 5 | $0.00012 | $0.00464 |
| Sonnet 5 | $0.00005 | $0.00186 |
| Haiku 4.5 | $0.00002 | $0.00093 |
Grade A, and why
project-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
專案初始化
PM 啟動新專案時使用,確保所有基礎結構就位。
使用方式
/project-kickoff <project-type> <project-name>
參數
$0: 專案類型(web-app / api-service / mobile-app / library)$ARGUMENTS: 完整參數
執行步驟
-
檢查現有結構
- 檢查 CLAUDE.md 是否已存在
- 檢查 .knowledge/ 目錄是否已存在
- 如已存在,提示確認是否覆蓋
-
部署 CLAUDE.md
- 從對應模板生成(替換
{專案名稱}佔位符) - 模板位置:AgentHub
.knowledge/company/project-templates/{type}/CLAUDE.md.template
- 從對應模板生成(替換
-
建立 .knowledge/ 結構
- 建立
.knowledge/目錄 - 複製
architecture.md(從模板目錄) - 建立空的
project-overview.md(標題 + 佔位符) - 建立空的
postmortem-log.md(標題 + 空表格) - 從模板部署
file-index.md(替換{專案名稱}、填入今日日期)- 模板位置:AgentHub
.knowledge/company/project-templates/{type}/file-index.md.template
- 模板位置:AgentHub
- 建立
-
部署共用規則
- 複製
company-rules.md→.knowledge/company-rules.md - 複製
team-workflow.md→.knowledge/team-workflow.md
- 複製
-
建立 Roadmap
5a. 建立
proposal/目錄(若已存在則跳過)5b. 建立
proposal/roadmap.md(若已存在則跳過):# {專案名稱} — 產品路線圖 ## 產品定位 > {一句話描述產品} ## 目標用戶 > {描述} ## 核心價值 > {描述} ## 版本規劃 | Sprint | 主題 | 目標 | 狀態 | |--------|------|------|------| | Sprint 1 | {待定} | {待定} | 🔲 規劃中 | ## 長期願景 > {描述} -
Git 初始化
6a. 檢查是否已有 git repo(
.git/目錄存在):- 已存在 → 跳過
git init - 不存在 → 執行
git init
6b. 建立
.gitignore(若已存在則跳過):node_modules/ dist/ .env .env.* .claude/ coverage/ *.log .DS_Store6c. 執行初始 commit(若 working tree 有變更):
git add -A git commit -m "chore: project kickoff — {project-name}" - 已存在 → 跳過
-
輸出下一步 Checklist
✅ 專案初始化完成 Git:已初始化 ✅ 初始 commit:chore: project kickoff — {project-name} ✅ Roadmap:proposal/roadmap.md ✅ 下一步: - [ ] 填寫 CLAUDE.md 專案簡介佔位符 - [ ] 填寫技術棧表格 - [ ] 填寫 proposal/roadmap.md 產品定位 - [ ] 執行 /product-diagnosis 做 G0 前置診斷 - [ ] 撰寫 Sprint 提案書(/sprint-proposal) - [ ] 執行 /dev-plan 建立 sprint branch
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 · 110 lines · 24 tokens per session scan A c7be468d5526
project-kickoff is a skill published in the GitHub repository Stanshy/AgentHub (201 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 929 once invoked, about $0.0001 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-30.
Other skills, from other repositories
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
integrated-browser
Use this when working on the VS Code integrated browser ("browserView") to understand its architecture and mental model. Covers the embedded Chromium browser, its editor tab, navigation, overlay/layout, sessions, and agent browser tools under src/vs/platform/browserView and src/vs/workbench/contrib/browserView.
agent-host-e2e-tests
Use when writing, recording, updating, validating, or troubleshooting the agent host end-to-end tests under src/vs/platform/agentHost/test/node/e2e (black-box tests that drive the whole agent host over the AHP protocol, using a CapiReplayProxy record/replay system for Claude/Copilot/Codex). Covers adding a…
vscode-dev-workbench
Use when the user wants to run the vscode.dev server locally and exercise the VS Code workbench or Agents window in the integrated browser against the local microsoft/vscode sources. Covers starting the dev server, the vscode-quality=dev URL, browser-driven interaction patterns, and optionally wiring up a local mock…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
thisWeek
Resolve "thisWeek" to a concrete ISO date range relative to your run time — this week so far (Monday → today). Returns inclusive civil dates plus exact UTC instants so you have temporal context without computing dates by hand. Read-only: no writes, no network. Use before a week-to-date task (this week's activity…