clawrium: Command for Claude Code

.opencode/commands/itx-plan-scaffold.md

itx-plan-scaffold is a command for Claude Code, OpenCode from ric03uec/clawrium. It costs 9 tokens per session (205 once invoked), scanned A, original, Apache-2.0.

A command that creates a phased implementation plan for a GitHub issue. It divides work by complexity and defines what each phase needs, changes, and must prove before completion.

In plain words
What is it for?
Use it to fetch an issue’s existing plan, choose phases, define entry and exit criteria, identify affected files, and create subtasks for larger work.
Why use it?
It turns a broad issue into ordered, checkable work and exposes dependencies before implementation begins.

Command for Claude CodeOpenCode

Written for Claude Code and OpenCode: $ARGUMENTS substitution, but also installed under .opencode/.

This is ric03uec/clawrium's own configuration. It tells Claude Code and OpenCode how to work on clawrium itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything clawrium configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ric03uec/clawrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ric03uec/clawrium/main/.opencode/commands/itx-plan-scaffold.md
Clone the repo
git clone --depth 1 https://github.com/ric03uec/clawrium

Made for: Claude Code, OpenCode.

Wrote 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.

agentmods badge for itx-plan-scaffold

README.md
[![agentmods](https://agentmods.dev/badge/commands/ric03uec/clawrium/itx-plan-scaffold.svg)](https://agentmods.dev/commands/ric03uec/clawrium/itx-plan-scaffold)
Your own site
<a href="https://agentmods.dev/commands/ric03uec/clawrium/itx-plan-scaffold"><img src="https://agentmods.dev/badge/commands/ric03uec/clawrium/itx-plan-scaffold.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 205 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00205
Opus 5 $0.00005 $0.00102
Sonnet 5 $0.00002 $0.00041
Haiku 4.5 $0.00001 $0.00020

Measured 7d ago against content hash 2794b58d79b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

itx-plan-scaffold 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 7d 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.

.opencode/commands/itx-plan-scaffold.md · 28 lines

What it actually says

Create a phased execution plan for GitHub issue $ARGUMENTS.

Steps:

  1. Fetch the issue with existing plan from comments
  2. Analyze complexity:
    • Simple (< 3 files): single-phase
    • Moderate (3-8 files): 2-3 phases
    • Complex (8+ files): multi-phase with subtasks
  3. For each phase, define:
    • Entry criteria (what must be true to start)
    • Exit criteria (tests, validation rules)
    • Dependencies (prerequisite phases)
    • Files affected
    • Complexity estimate
  4. Post scaffolding as a comment
  5. Create subtask issues if multi-phase
  6. Update labels: plannedready

Ordering rules:

  • Foundation phases first (schemas, models)
  • Core logic second (services, business rules)
  • Integration third (APIs, handlers)
  • Presentation last (UI, docs)
Changes

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.

  1. 7d ago First seen · 28 lines · 9 tokens per session scan A 2794b58d79b5

Subscribe to this mod's changes

itx-plan-scaffold is a command published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 3d ago), licensed Apache-2.0. It adds 9 tokens to every session and 205 once invoked, about $0.0000 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.