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 skills add CassetteTapeCrackle/claude-starters --skill clean-code-cgit clone --depth 1 https://github.com/CassetteTapeCrackle/claude-startersWrote 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/cassettetapecrackle/claude-starters/clean-code-c)<a href="https://agentmods.dev/skills/cassettetapecrackle/claude-starters/clean-code-c"><img src="https://agentmods.dev/badge/skills/cassettetapecrackle/claude-starters/clean-code-c/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/cassettetapecrackle/claude-starters/clean-code-c"><img src="https://agentmods.dev/badge/skills/cassettetapecrackle/claude-starters/clean-code-c.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00318 |
| Opus 5.5 | $0.00014 | $0.00127 |
| Sonnet 5.5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
clean-code-c 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 1mo 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
Clean-code C (depth)
On top of the base rules (C11, CMake, clang-tidy, ASan+UBSan, Unity/CMocka).
Memory & ownership
- Document ownership at every allocating function: who frees, when. One owner; transfer explicitly.
- Check every
malloc/realloc/callocreturn. Free on every path (goto-cleanup pattern for multi-resource functions). - Set freed pointers to
NULLif reused. Never return pointers to stack locals.
Safety
- No VLAs; no unbounded
strcpy/strcat/sprintf— usesnprintfand bounded copies with explicit sizes. sizeof(*ptr)(variable) oversizeof(Type)so it survives type changes. Initialize every variable at declaration.
Structure
staticfor internal-linkage functions/globals; expose the minimum in headers.const-correct parameters;size_tfor sizes/indices. Small functions; early returns; one responsibility per file.
Smells
- An allocation whose free path isn't obvious → add the ownership comment or restructure with goto-cleanup.
sprintf/strcpyinto a fixed buffer → bounded call.- Uninitialized variable read (UBSan will catch it) → initialize at declaration.
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.
- 1mo ago First seen · 27 lines · 34 tokens per session scan A 78a93d00121f
clean-code-c is a skill published in the GitHub repository CassetteTapeCrackle/claude-starters (1 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 318 once invoked, about $0.0001 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-31.
Other skills, from other repositories
cpp-coding-standards
C++ coding standards based on the C++ Core Guidelines (isocpp.github.io). Use when writing, reviewing, or refactoring C++ code to enforce modern, safe, and idiomatic practices.
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
stack-pr
Use when breaking a too-big branch into a stack of smaller chained PRs — commit-based default, --smart agent-reshape, gh-stack detection, cross-links. Invoked by /orc:stack-pr and /orc:ship's size gate.
review-contract
The canonical review findings contract — JSON schema, severity enum, mechanical severity→event mapping, confidence ≥0.8 rule.
turborepo
Turborepo monorepo build-system guidance — turbo.json task pipelines, caching, the turbo CLI, --filter/--affected, CI, env vars, and packages.
caveman-review
Ultra-compressed code review comments — one line per finding: location, problem, fix.