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.
curl -O https://raw.githubusercontent.com/ric03uec/clawrium/main/.claude/skills/itx-release/SKILL.mdgit 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/skills/ric03uec/clawrium/itx-release)<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-release"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-release.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.00023 | $0.02680 |
| Opus 5 | $0.00012 | $0.01340 |
| Sonnet 5 | $0.00005 | $0.00536 |
| Haiku 4.5 | $0.00002 | $0.00268 |
Grade A, and why
itx-release 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Cut a new clawrium release end-to-end: bump version, sync docs, open a release PR, tag, trigger the PyPI publish workflow, and verify.
Inputs
$ARGUMENTS(optional): target version (e.g.26.5.2or26.6.0). If omitted, ask the user.
Files this skill updates (the "known set")
Hard-coded list. The skill will edit exactly these and warn if it finds version-shaped strings elsewhere that look stale.
| File | What to update |
|---|---|
pyproject.toml |
version = "<NEW>" (line near top) |
uv.lock |
Re-run uv sync after editing pyproject.toml; the clawrium entry's version updates as a derived artifact. Stage and commit alongside pyproject.toml. |
AGENTS.md |
- Version: <NEW> line |
docs/installation.md |
clawrium==<NEW> and clawctl, version <NEW>. Canonical install doc — edit this first, then mirror body verbatim into website/docs/installation.md. |
website/docs/installation.md |
clawrium==<NEW> and clawctl, version <NEW>. Mirror of docs/installation.md; body must stay identical (only the Docusaurus frontmatter and mirror-warning comment at the top differ). |
website/docs/guides/quickstart.md |
clawrium==<NEW> |
website/docs/scenarios/101.md |
clawctl <NEW> |
CHANGELOG.md (root) |
Archive the current contents to docs/releases/<NEW>/CHANGELOG.md, then reset this file to the empty [Unreleased] template. See Phase 1 step 6a. |
docs/releases/<NEW>/CHANGELOG.md |
New per-release archive folder created from the root changelog at cut time. See Phase 1 step 6a. |
Do NOT touch:
docs/agent-support/hermes.md— that's the hermes upstream agent version, not clawrium.website/package.json,gui/package.json— independent subpackages.src/clawrium/platform/registry/**andtests/**— those are agent-type fixtures, not clawrium's version.
Instructions
Phase 0 — Pre-flight
- Determine target version. If
$ARGUMENTSis empty, read current frompyproject.toml:
Ask the user: "Current isCURRENT=$(grep -m1 '^version' pyproject.toml | sed 's/.*"\(.*\)"/\1/')$CURRENT. Target version?" Stop until answered.
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.
- 2d ago Changed · -1 lines · -1 tokens per session 17cf50642ee6
- 6d ago First seen · 221 lines · 24 tokens per session scan A c4def40dbaef
itx-release is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 2,680 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
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
conventional-commit
Conventional Commit - Generate Conventional Commits 1.0.0 compliant messages. MANDATORY for all git commits. Invoke when user says 'commit', 'commit this', or asks to commit code.
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
gwm
Manage git worktrees across any repository with the gwm Rust binary (CLI + ratatui TUI). Use when the user asks to create / list / remove / bootstrap / switch / link worktrees, run a command across worktrees (gwm exec) or reclaim build artifacts (gwm clean), materialise a PR into a worktree (gwm review), drive a…