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 commands/ric03uec/clawrium/itx-plan-creategit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/ric03uec/clawrium/itx-plan-create)<a href="https://agentmods.dev/commands/ric03uec/clawrium/itx-plan-create"><img src="https://agentmods.dev/badge/commands/ric03uec/clawrium/itx-plan-create.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.00011 | $0.00146 |
| Opus 5 | $0.00005 | $0.00073 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
itx-plan-create 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.
What it actually says
Create a detailed implementation plan for GitHub issue $ARGUMENTS.
Steps:
- Fetch the issue:
gh issue view $ARGUMENTS --json number,title,body,labels,comments - Explore the codebase to understand scope
- Create a high-level plan with:
- Product output (what the user gets)
- Technical details (files, modules affected)
- Implementation steps
- Test strategy
- Post the plan as a comment on the issue
- Update labels:
planning→planned
If the issue is complex (multiple files/concerns), create subtasks.
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 · 19 lines · 11 tokens per session scan A b03540defa67
itx-plan-create is a command published in the GitHub repository ric03uec/clawrium (51 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 146 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 commands, from other repositories
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
update-python-version
Update the minimum Python version requirement across the entire codebase.
execute-pydantic-ai-prp
Implement a Pydantic AI agent using the PRP file.
init
Command "init" from ErisPulse/ErisPulse, covering erispulse.cli.commands.init 模块, 模块概述, 函数列表, validateprojectname(name: str) and 类列表.
install
Command "install" from ErisPulse/ErisPulse, covering erispulse.cli.commands.install 模块, 模块概述, 类列表 and class installcommand(command).