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-bug-new/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-bug-new)<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>- NVIDIA SkillSpector pass
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.00015 | $0.00885 |
| Opus 5 | $0.00008 | $0.00443 |
| Sonnet 5 | $0.00003 | $0.00177 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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.
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
-
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.)
-
Ask for Customer Outcome: Use
AskUserQuestionto 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"
-
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
- Format:
-
Gather Details:
- If the user provided a description argument, use it for context
- Identify steps to reproduce if available
- Note environment details
-
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 -
Create Issue: Use
gh issue createwith:gh issue create \ --title "<customer outcome from step 3>" \ --label "bug" \ --label "needs-triage" \ --body "<structured bug report>" -
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>
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.
- 4d ago Changed · -1 lines f7ea376182e4
- 8d ago First seen · 123 lines · 15 tokens per session scan A 02d1a35e9e6a
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.
Other skills, from other repositories
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
dd-symdb
Symbol Database - search service symbols, find probe-able methods.