itx-plan-create

itx-plan-create is a skill for Claude Code, Codex from ric03uec/clawrium. It costs 16 tokens per session (1,091 once invoked), scanned A, original, Apache-2.0.

A workflow for creating a high-level implementation plan from a GitHub issue. It examines the issue, the codebase, related modules, dependencies, and existing tests before outlining the work.

In plain words
What is it for?
Use it to plan software changes, document the plan in the repository, define a test strategy, and create linked GitHub subtasks when the work is complex.
Why use it?
It turns a problem report into an actionable plan with affected files, testing needs, and possible risks. Larger changes can be split into linked subtasks.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/ric03uec/clawrium/itx-plan-create
Any agent
npx skills add ric03uec/clawrium --skill itx-plan-create
Clone the repo
git clone --depth 1 https://github.com/ric03uec/clawrium

Made for: Claude Code, Codex.

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-create

README.md
[![agentmods](https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-plan-create.svg)](https://agentmods.dev/skills/ric03uec/clawrium/itx-plan-create)
Your own site
<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-plan-create"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-plan-create.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,091 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00016 $0.01091
Opus 5 $0.00008 $0.00545
Sonnet 5 $0.00003 $0.00218
Haiku 4.5 $0.00002 $0.00109

Measured yesterday against content hash 47ebe4f21d35, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

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.

.claude/skills/itx-plan-create/SKILL.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Implementation Planning (Create Phase)

Create a high-level implementation plan for a GitHub issue with product output and technical details.

Instructions

  1. Fetch Issue: Get full issue details

    gh issue view <number> --json number,title,body,labels,comments
    
  2. Explore Codebase: Understand the scope

    • Identify affected files and modules
    • Review related code patterns
    • Check for existing tests
    • Note any dependencies
  3. Create Plan: Structure the implementation approach

    • Break down into logical steps
    • Identify files to modify/create
    • Define test strategy
    • Note potential risks
  4. Save Plan to File:

    mkdir -p .itx/<number>
    # Write plan to .itx/<number>/00_PLAN.md
    
  5. Decide on Subtasks:

    • Simple issue (< 3 files, single concern): No subtasks needed
    • Complex issue (multiple files, multiple concerns): Create subtasks
  6. If Subtasks Needed: Detect repository info and create subtask issues with sub-issue links

    # Extract repository info
    REMOTE_URL=$(git config --get remote.origin.url)
    OWNER_REPO=$(echo "$REMOTE_URL" | sed -E 's/.*[:/]([^/]+\/[^/]+)(\.git)?$/\1/')
    OWNER=$(echo "$OWNER_REPO" | cut -d'/' -f1)
    REPO=$(echo "$OWNER_REPO" | cut -d'/' -f2)
    
    # Create subtask
    CHILD_URL=$(gh issue create \
      --title "[Parent #<parent>] <subtask description>" \
      --label "ready" \
      --body "<subtask details>")
    CHILD_NUM=$(basename $CHILD_URL)
    
    # Link as sub-issue using GraphQL with dynamic repo
    gh api graphql -f query='
      mutation($parentId: ID!, $childId: ID!) {
        addSubIssue(input: {issueId: $parentId, subIssueId: $childId}) {
          issue { number }
          subIssue { number }
        }
      }' \
      -f parentId=$(gh api graphql -f query='query($owner: String!, $repo: String!, $issue: Int!) { repository(owner: $owner, name: $repo) { issue(number: $issue) { id } } }' -f owner="$OWNER" -f repo="$REPO" -F issue=$PARENT_NUM | jq -r '.data.repository.issue.id') \
      -f childId=$(gh api graphql -f query='query($owner: String!, $repo: String!, $issue: Int!) { repository(owner: $owner, name: $repo) { issue(number: $issue) { id } } }' -f owner="$OWNER" -f repo="$REPO" -F issue=$CHILD_NUM | jq -r '.data.repository.issue.id')
    

Read the full file on GitHub · 132 lines

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. yesterday Changed · -1 lines · -1 tokens per session 47ebe4f21d35
  2. 5d ago First seen · 133 lines · 17 tokens per session scan A 98a06a818e30

Subscribe to this mod's changes

itx-plan-create is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,091 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.

Related

Other skills, from other repositories

load-github-action-thread

Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.

astral-sh/uv · 62 tokens

uv-mapping

Inspect, generate, transform, and visualize UV channels on StaticMesh assets (UVMappingService). Use when the user asks to check/add/remove UV channels, auto-unwrap UVs, transform (tile/offset/rotate) UVs, check UV health/islands, or export a UV layout image.

kevinpbuckley/VibeUE · 65 tokens

depsguard

Install and run DepsGuard, a zero-dependency CLI that scans and fixes package manager configs (npm, pnpm, yarn, bun, uv) for supply chain security best practices.

arnica/depsguard · 41 tokens

python

Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…

ericrisco/rsc-harness · 94 tokens

deploying-osquery-for-endpoint-monitoring

Deploys and configures osquery for real-time endpoint monitoring using SQL-based queries to inspect running processes, open ports, installed software, and system configuration. Use when building visibility into endpoint state, threat hunting across fleet, or implementing compliance monitoring. Activates for requests…

26zl/cybersec-toolkit · 80 tokens

aget-propose-actions

Propose ranked next-best actions with evidence grounding, time budgets, and execute-all default. Formalizes the fleet's highest-frequency interaction pattern.

aget-framework/aget · 33 tokens