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/crbnos/carbon/root-causenpx skills add crbnos/carbon --skill root-causegit clone --depth 1 https://github.com/crbnos/carbonWrote 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/crbnos/carbon/root-cause)<a href="https://agentmods.dev/skills/crbnos/carbon/root-cause"><img src="https://agentmods.dev/badge/skills/crbnos/carbon/root-cause.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 | $0.00096 | $0.01535 |
| Opus 5 | $0.00048 | $0.00767 |
| Sonnet 5 | $0.00019 | $0.00307 |
| Haiku 4.5 | $0.00010 | $0.00153 |
Grade A, and why
root-cause 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 First seen · 134 lines · 96 tokens per session scan A e0665027ec98
root-cause is a skill published in the GitHub repository crbnos/carbon (2,393 stars, last pushed today), with no licence file. It adds 96 tokens to every session and 1,535 once invoked, about $0.0005 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-ts
TypeScript code shape inside a well-named module — taste, not lint. Prefer one class or namespace per file (the unit a test targets) over scattered free exports; consolidate related code, don't fragment. The unit of code should be the unit of spec. Use when authoring TS in editor/grida-canvas, editor/lib/, or…
balance
Остатки по складу или денежные остатки из 1С.
env-management
Environment variable patterns for Python (python-dotenv, Pydantic BaseSettings) and TypeScript (VITE, NEXTPUBLIC) projects — .env.example authorship, schema validation, mock/feature flags, and safe defaults — synthesized from lead-gen-engine and seo-geo-aeo-engine.
nodejs-sdk
Type-safe Node.js API client SDK with validation, mocking, retry, and logging. Use when building API clients for Node.js applications.
nuxt-modules
Use when creating Nuxt modules: (1) Published npm modules (@nuxtjs/, nuxt-), (2) Local project modules (modules/ directory), (3) Runtime extensions (components, composables, plugins), (4) Server extensions (API routes, middleware), (5) Releasing/publishing modules to npm, (6) Setting up CI/CD workflows for modules.…
ts-library
Use when authoring TypeScript libraries or npm packages - covers project setup, package.json exports, build tooling (tsdown/unbuild), API design patterns, type inference tricks, testing, and publishing to npm. Use when bundling, configuring dual CJS/ESM output, or setting up release workflows.