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 darellchua2/opencode-config-template --skill clean-code-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/clean-code-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/clean-code-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/clean-code-skill.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.1 | $0.00034 | $0.06866 |
| Opus 5 | $0.00017 | $0.03433 |
| Sonnet 5 | $0.00007 | $0.01373 |
| Haiku 4.5 | $0.00003 | $0.00687 |
Grade C, and why
clean-code-skill scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
When protocol is enabled, this skill defaults to `Iterations: 10` (sufficient for typical single-pass workflows). Override with `Iterations: N` for specific tasks. Safety blocks: `.env`, `node_modules/`, `rm -rf`, `git p How it starts
The opening of the file, as written. The whole thing — 935 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I help you write clean, maintainable code that is easy to understand and change:
- Improve Naming: Apply consistent, understandable, specific, and searchable naming conventions
- Reduce Function Size: Keep functions small (under 10 lines) with single responsibility
- Apply Object Calisthenics: Follow the 9 rules for better object-oriented design
- Eliminate Comments: Replace comments with self-documenting code
- Improve Formatting: Apply consistent code structure and organization
- Reduce Cognitive Load: Write code that tells a story
When to use me
Use this skill when:
- Code is hard to understand even though it works
- Functions are long and do multiple things
- Names are vague, inconsistent, or misleading
- Code requires extensive comments to explain what it does
- Reviewing code for readability and maintainability
- Onboarding new developers who struggle with the codebase
- Setting up coding standards for a team
- Refactoring legacy code for better maintainability
Prerequisites
- Code to analyze or write
- Understanding of basic programming concepts
- Willingness to refactor for readability
- Knowledge of the domain/business context for naming
What is Clean Code?
Code that is:
- Easy to understand - reveals intent clearly
- Easy to change - modifications are localized
- Easy to test - dependencies are injectable
- Simple - no unnecessary complexity
The Human-Centered Approach
Code has THREE consumers:
- Users - get their needs met
- Customers - make or save money
- Developers - must maintain it
Design for all three, but remember: developers read code 10x more than they write it.
Naming Principles
Priority Order for Naming
- Consistency & Uniqueness (HIGHEST PRIORITY)
- Understandability
- Specificity
- Brevity
- Searchability
- Pronounceability
- Austerity
1. Consistency & Uniqueness
Same concept = same name everywhere. One name per concept.
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 First seen · 935 lines · 34 tokens per session scan C 3274c5600312
clean-code-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 6,866 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
dorodango
Polishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.
ring:exploring-codebases
Exploring a codebase across phases: scopes the target, detects architecture, components, and layers, deep-dives each discovered perspective, then synthesizes findings into actionable guidance with file:line evidence. Use to understand how a feature or system works before planning changes, or to orient on an unfamiliar…
ring:searching-code
Forensic code search and analysis with optional Chain of Draft (CoD) ultra-concise mode. Five-phase methodology (clarification, planning, execution, analysis, synthesis) with severity assessment. Use for targeted investigation of specific patterns, bugs, or vulnerabilities. Skip for broad architecture mapping (use…
ring:planning-codebase-simplification
Planning a whole-codebase simplification: audits a Go/TS codebase for needless abstraction and emits a KILL/REVIEW/KEEP plan plus a ring:running-dev-cycle task array. Plans only — no edits. Detects single-impl interfaces, pass-through shims, translation-free adapters, and dead-code cascade chains under an inverted…