clawrium: Skill for Claude Code

.claude/skills/itx-issue-update/SKILL.md

itx-issue-update is a skill for Claude Code from ric03uec/clawrium. It costs 13 tokens per session (348 once invoked), scanned A, original, Apache-2.0.

A GitHub issue command that adds a comment to an existing issue. It works with any issue type, such as a bug or feature request.

In plain words
What is it for?
Use it to post supplied text to an issue by number, including relevant technical details and a record of the request.
Why use it?
It gives maintainers a consistent way to record progress or findings directly on an issue and warns when the issue is already closed.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions AGENTS.md.

This is ric03uec/clawrium's own configuration. It tells Claude Code 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/.claude/skills/itx-issue-update/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ric03uec/clawrium

Made for: Claude Code.

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-issue-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-issue-update.svg)](https://agentmods.dev/skills/ric03uec/clawrium/itx-issue-update)
Your own site
<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-issue-update"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-issue-update.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 348 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00013 $0.00348
Opus 5 $0.00006 $0.00174
Sonnet 5 $0.00003 $0.00070
Haiku 4.5 $0.00001 $0.00035

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

Security

Grade A, and why

itx-issue-update 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 3d 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.

.claude/skills/itx-issue-update/SKILL.md · 66 lines

What it actually says

Issue Update

Add a comment to an existing GitHub issue.

Instructions

  1. Parse Arguments: Extract issue number and comment text from arguments

    • First argument: issue number (required)
    • Remaining text: comment content (required)
  2. Validate Issue: Verify the issue exists

    gh issue view <number> --json number,title,state
    
  3. Add Comment: Post the comment with prompt log

    gh issue comment <number> --body "<comment with prompt log>"
    
  4. Comment Format:

    <comment text>
    
    ---
    
    <details>
    <summary>Prompt Log</summary>
    
    **Stage**: issue-update
    **Skill**: /itx-issue-update
    **Timestamp**: <ISO timestamp>
    **Model**: <model>
    
    ```prompt
    <original user prompt that triggered this update>
    
  5. Return: Confirmation with issue URL

Examples

/itx-issue-update 28 Updated the plan to include prompt logging requirement

Notes

  • Works for any issue type (bug, feature, etc.)
  • Warn if the issue is closed

Prompt Logging

REQUIRED: Append prompt log to .itx/<N>/00_PLAN.md.

See AGENTS.md for format specification.

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. 3d ago Changed · -1 lines fe0894156f75
  2. 7d ago First seen · 67 lines · 13 tokens per session scan A 2788b14e2a1e

Subscribe to this mod's changes

itx-issue-update is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 4d ago), licensed Apache-2.0. It adds 13 tokens to every session and 348 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

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

creating-snippets

Use when creating, editing, validating, testing, running, explaining, or removing Labby Code Mode snippets; when a user wants a reusable workflow made from gateway MCP tools; or when building schema-backed snippets from upstream tool ids, JSON schemas, params, inputs, defaults, artifacts, and MCP/CLI snippet actions.

dinglebear-ai/labby · 68 tokens

using-labby

Use when operating Labby through its CLI, MCP, HTTP API, or web UI; installing or updating Labby; configuring LABBYHOME; bootstrapping, repairing, or rolling back an Incus gateway or host service; exporting, verifying, or restoring durable state; checking health or logs; managing gateway upstreams, OAuth, or protected…

dinglebear-ai/labby · 86 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens