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 | $0.00017 | $0.00159 |
| Sonnet 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 8d 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.
- 8d 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 20d ago), licensed MIT. It adds 34 tokens to every session and 318 once invoked, about $0.0002 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-31.
Other skills, from other repositories
spec-implement
Continue an approved Spec-backed workflow when the user says "implement", "go", "start", or "do it". After Codex Plan Mode, persist the next missing design.md or plan.json artifact and stop. When both artifacts exist, execute plan.json with TDD and report between batches.
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…
project-setup
Setup and hardening review for cross-platform modern-C++ (C++17) native projects, especially Node.js addons built with node-gyp / node-addon-api. Use when asked to "set up a native addon", "harden a C/C++ build", "review my binding.gyp", "add compiler hardening flags", "wire up AddressSanitizer/UBSan/TSan/clang-tidy"…
cpp-reinforcement-learning
C++ Reinforcement Learning best practices using libtorch (PyTorch C++ frontend) and modern C++17/20. Use when: Implementing RL algorithms in C++ for performance-critical applications Building production RL systems with libtorch Creating replay buffers and experience storage Optimizing RL training with GPU acceleration…
esp32-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting C++ firmware for ESP32 and variants (ESP32-S2, S3, C3, C6, H2, P4) using ESP-IDF or PlatformIO. Provides expert critique covering FreeRTOS task design, memory management (IRAM/DRAM/PSRAM), peripheral drivers (I2C/SPI/UART/GPIO)…
cpp-specifications
Structural verification and quality patterns for C and C++ — sanitizers (ASAN/UBSAN/TSAN/MSAN), const correctness, ownership, thread safety, modern idioms. Load when planning, implementing, or reviewing C/C++ code (.c, .cc, .cpp, .h, .hpp; CMake, Makefile).