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.
git clone --depth 1 https://github.com/xyzbit/claude-pluginsWrote 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/commands/xyzbit/claude-plugins/project-init)<a href="https://agentmods.dev/commands/xyzbit/claude-plugins/project-init"><img src="https://agentmods.dev/badge/commands/xyzbit/claude-plugins/project-init/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/commands/xyzbit/claude-plugins/project-init"><img src="https://agentmods.dev/badge/commands/xyzbit/claude-plugins/project-init.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.00020 | $0.00273 |
| Opus 5.5 | $0.00008 | $0.00109 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
project-init 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 1mo 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
Project Init
初始化一个新项目。此命令仅需执行一次，用于搭建项目骨架、创建配置文件和需求管理目录。
执行流程
第一步：解析参数
从用户输入中提取：
- 项目名称（必须）
- 是否使用模板（可选，用户说"不用模板"或传
--no-template时为否，默认为是）
第二步：检查项目是否已存在
ls <项目名称>/.dev-enegine/.lra-config.json 2>/dev/null && echo "PROJECT_EXISTS" || echo "NEW_PROJECT"
如果项目已存在，提示用户并终止。
第三步：调用 Initializer Agent
将项目名称和模板选项传递给 Initializer Agent 子代理。
Initializer Agent 将初始化项目骨架并完成首次提交。
注意事项
- 此命令仅用于首次初始化，不要用于需求开发
- 初始化完成后，使用
/requirement-dev进行需求开发
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.
- 1mo ago First seen · 37 lines · 20 tokens per session scan A c7dd4c92c51a
project-init is a command published in the GitHub repository xyzbit/claude-plugins (29 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 20 tokens to every session and 273 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.