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-verify/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-verify)<a href="https://agentmods.dev/skills/ric03uec/clawrium/itx-verify"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/itx-verify.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.00014 | $0.00593 |
| Opus 5 | $0.00007 | $0.00296 |
| Sonnet 5 | $0.00003 | $0.00119 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
itx-verify 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification
Run all verification checks to ensure code quality.
Instructions
-
Load Configuration:
ITX_CONFIG="$(git rev-parse --show-toplevel)/.claude/itx-config.json" if [ -f "$ITX_CONFIG" ]; then TEST_CMD=$(jq -r '.build.test_command // "make test"' "$ITX_CONFIG") LINT_CMD=$(jq -r '.build.lint_command // "make lint"' "$ITX_CONFIG") COV_CMD=$(jq -r '.build.coverage_command // "make test-cov"' "$ITX_CONFIG") else TEST_CMD="make test" LINT_CMD="make lint" COV_CMD="make test-cov" fi -
Run Tests:
$TEST_CMD- All tests must pass
- Note any failures with details
-
Run Linter:
$LINT_CMD- All lint checks must pass
- Fix any issues found
-
Check Coverage (optional):
$COV_CMD- Review coverage for new code
- Ensure critical paths are tested
-
Report Results:
## Verification Results ### Tests - Command: <test command> - Status: PASS/FAIL - Details: <summary> ### Lint - Command: <lint command> - Status: PASS/FAIL - Details: <summary> ### Coverage - Status: <percentage> - New code coverage: <assessment> -
If Failures:
- Fix issues
- Re-run verification
- Iterate until all checks pass
Configuration
Customize build commands in .claude/itx-config.json:
{
"build": {
"test_command": "npm test",
"lint_command": "npm run lint",
"coverage_command": "npm run test:coverage"
}
}
Defaults (no config):
test_command:make testlint_command:make lintcoverage_command:make test-cov
Notes
- This is a local operation
- Must pass before creating PRs
- Use this after making changes, before committing
- Can be run multiple times during development
Prompt Logging
REQUIRED: Append prompt log to .itx/<N>/02_VERIFY.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.
- 3d ago Changed · -1 lines af6def927a76
- 8d ago First seen · 104 lines · 14 tokens per session scan A a215ff184cd0
itx-verify is a skill published in the GitHub repository ric03uec/clawrium (51 stars, last pushed 4d ago), licensed Apache-2.0. It adds 14 tokens to every session and 593 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
review-work
Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…
remove-ai-slops
Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel deep agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
check
Auto-fix lint and formatting, then report types and tests. Run before every commit.
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…