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.
npx agentmods add skills/ric03uec/clawrium/itx-bug-updatenpx skills add ric03uec/clawrium --skill itx-bug-updategit 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-update)<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-bug-update"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-bug-update.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.00014 | $0.00369 |
| Opus 5 | $0.00007 | $0.00185 |
| Sonnet 5 | $0.00003 | $0.00074 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
itx-bug-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 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.
What it actually says
Bug Update
Add a comment to an existing GitHub bug issue.
Instructions
-
Parse Arguments: Extract issue number and comment text from arguments
- First argument: issue number (required)
- Remaining text: comment content (required)
-
Validate Issue: Verify the issue exists and has
buglabelgh issue view <number> --json number,title,labels -
Add Comment: Post the comment with prompt log
gh issue comment <number> --body "<comment with prompt log>" -
Comment Format:
<comment text> --- <details> <summary>Prompt Log</summary> **Stage**: bug-update **Skill**: /itx-bug-update **Timestamp**: <ISO timestamp> **Model**: <model> ```prompt <original user prompt that triggered this update> -
Return: Confirmation with issue URL
Examples
/itx-bug-update 42 Added debug logging, the error occurs in registry.py line 156
Notes
- Warn if the issue doesn't have a
buglabel (may be wrong issue type) - Include relevant technical details from the conversation
Prompt Logging
REQUIRED: Append prompt log to .itx/<N>/00_PLAN.md.
See AGENTS.md for format specification.
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 892b23cb7ad6
- 6d ago First seen · 67 lines · 14 tokens per session scan A abfe50196067
itx-bug-update is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 2d ago), licensed Apache-2.0. It adds 14 tokens to every session and 369 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
aget-check-evolution
Monitor .aget/evolution/ directory health. Validates file counts, naming conventions, disk usage, and returns health status with alerts on anomalies.
aget-handle-incident
Handle incidents with diagnosis and mitigation.
aget-lint-code
Run code linting and formatting checks.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.