Borrowing it
Nothing to install: this file belongs to crbnos/carbon. 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/crbnos/carbon/main/.claude/skills/spec-writing/SKILL.mdgit 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/spec-writing)<a href="https://agentmods.dev/skills/crbnos/carbon/spec-writing"><img src="https://agentmods.dev/badge/skills/crbnos/carbon/spec-writing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/crbnos/carbon/spec-writing"><img src="https://agentmods.dev/badge/skills/crbnos/carbon/spec-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 98 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Excessive Agency · line 184 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00119 | $0.03322 |
| Opus 5.5 | $0.00048 | $0.01329 |
| Sonnet 5.5 | $0.00024 | $0.00664 |
| Haiku 4.5 | $0.00012 | $0.00332 |
Grade A, and why
spec-writing 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 17d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 17d ago Changed · +8 lines 6f73a663838c
- 22d ago Changed 2c15a1718e3e
- 26d ago Changed · +59 lines 5b067fb8c3ea
- 2mo ago First seen · 197 lines · 119 tokens per session scan A d15d0e2d73f9
spec-writing is a skill published in the GitHub repository crbnos/carbon (2,783 stars, last pushed today), with no licence file. It adds 119 tokens to every session and 3,322 once invoked, about $0.0005 per session on Opus 5.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
readme-writing-readme-files
README quality standards for engaging, accessible, scannable content including problem-solution hooks, plain language (no unexplained jargon), acronym context, paragraph limits (≤5 lines), benefits-focused language, visual hierarchy, and progressive disclosure. Essential for creating effective README files that…
docs-validating-software-engineering-separation
Validates software engineering documentation separation between OSE Platform style guides (docs/explanation/) and AyoKoding educational content (apps/ayokoding-www/). Ensures no duplication, proper prerequisite statements, and style guide focus on repository-specific conventions only.
docs-validating-links
Link validation methodology for markdown links including format requirements, path validation, broken link detection, external link verification, and checker implementation patterns.
specs-validating-structure
Validation methodology for specs/ folders — nine categories covering README/feature-file structural completeness, Gherkin format compliance, cross-folder consistency, C4 diagrams, cross-references, spec-to-implementation alignment, tree-shape compliance, and BDD/contracts adoption gaps. Used by specs-checker and…
docs-converting-pdf-to-markdown
PDF-to-Markdown conversion fidelity — the crane CLI, criticality levels, and workflow steps shared by the pdf-to-md maker/checker/fixer family.
specs-scaffolding
Mechanics for specs-maker — the four surface-profile directory trees, README/feature-file/C4-diagram content generation, and the PM-readability/placement/structure conventions every scaffolded file follows.