clawrium: Skill for Claude Code

.claude/skills/itx-bug-new/SKILL.md

itx-bug-new is a skill for Claude Code from ric03uec/clawrium. It costs 15 tokens per session (885 once invoked), scanned A, original, Apache-2.0.

A workflow for creating a GitHub issue that reports a software bug using details from the current conversation.

In plain words
What is it for?
Use it to review the conversation, gather the desired fix outcome, form an issue title, and prepare a GitHub bug report.
Why use it?
It turns scattered error messages, reproduction steps, and environment details into a structured issue. It also asks what the user should be able to do after the bug is fixed.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: names the AskUserQuestion tool; 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-bug-new/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-bug-new

README.md
[![agentmods](https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-bug-new.svg)](https://agentmods.dev/skills/ric03uec/clawrium/itx-bug-new)
Your own site
<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-bug-new"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-bug-new.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 885 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.00015 $0.00885
Opus 5 $0.00008 $0.00443
Sonnet 5 $0.00003 $0.00177
Haiku 4.5 $0.00002 $0.00089

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

Security

Grade A, and why

itx-bug-new 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.

.claude/skills/itx-bug-new/SKILL.md · 122 lines

How it starts

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

Bug Report Creation

Create a GitHub issue for a bug based on the current conversation context.

Instructions

  1. Analyze Context: Review the current conversation for:

    • Error messages and stack traces
    • Unexpected behavior descriptions
    • Steps that led to the issue
    • Environment details (version, OS, etc.)
  2. Ask for Customer Outcome: Use AskUserQuestion to ask:

    "What should the user be able to do when this bug is fixed?"

    Example outcomes:

    • "User can install dependencies without version mismatch errors"
    • "User can add resources with special characters in names"
    • "User can run status command without timeout"
  3. Form Issue Title: Use the customer outcome as the issue title.

    • Format: <outcome> (what the user can do after fix)
    • Example: "User can install dependencies without version mismatch errors"
    • The user can change this later if needed
  4. Gather Details:

    • If the user provided a description argument, use it for context
    • Identify steps to reproduce if available
    • Note environment details
  5. Load Project Name (for environment section):

    ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json"
    if [ -f "$ITX_CONFIG" ]; then
      PROJECT_NAME=$(jq -r '.project.name // ""' "$ITX_CONFIG")
      VERSION_LABEL=$(jq -r '.project.version_label // "Version"' "$ITX_CONFIG")
    fi
    
    # Fallback: use repository name if no config
    if [ -z "$PROJECT_NAME" ]; then
      REMOTE_URL=$(git config --get remote.origin.url)
      PROJECT_NAME=$(echo "$REMOTE_URL" | sed -E 's/.*[:/]([^/]+\/[^/]+)(\.git)?$/\1/' | cut -d'/' -f2)
    fi
    
  6. Create Issue: Use gh issue create with:

    gh issue create \
      --title "<customer outcome from step 3>" \
      --label "bug" \
      --label "needs-triage" \
      --body "<structured bug report>"
    
  7. Bug Report Body Format:

    ## Customer Outcome
    <The outcome statement - what user can do when fixed>
    
    ## Description
    <What is currently happening / the bug>
    
    ## Steps to Reproduce
    1. <step>
    2. <step>
    
    ## Expected Behavior
    <What should happen>
    
    ## Actual Behavior
    <What actually happens>
    
    ## Environment
    - <project name> version: <version>
    - Platform: <os/platform>
    - Other relevant details: <details>
    
    ---
    
    <details>
    <summary>Prompt Log</summary>
    
    **Stage**: bug-creation
    **Skill**: /itx-bug-new
    **Timestamp**: <ISO timestamp>
    **Model**: <model>
    
    ```prompt
    <original user prompt/context that led to this bug>
    

Read the full file on GitHub · 122 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. 4d ago Changed · -1 lines f7ea376182e4
  2. 8d ago First seen · 123 lines · 15 tokens per session scan A 02d1a35e9e6a

Subscribe to this mod's changes

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