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 ChenShuo2004/cs-skills --skill cs-clean-codegit clone --depth 1 https://github.com/ChenShuo2004/cs-skillsWrote 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/chenshuo2004/cs-skills/cs-clean-code)<a href="https://agentmods.dev/skills/chenshuo2004/cs-skills/cs-clean-code"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-clean-code/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/chenshuo2004/cs-skills/cs-clean-code"><img src="https://agentmods.dev/badge/skills/chenshuo2004/cs-skills/cs-clean-code.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Excessive Agency · line 111 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.00054 | $0.00655 |
| Opus 5.5 | $0.00022 | $0.00262 |
| Sonnet 5.5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
cs-clean-code 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 19d 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
CS Clean Code
让实现符合需求，降低维护成本。保留现有框架、公共接口与用户改动；不为风格一致重写可用模块。
先定位再修改
读取拥有该行为的代码、相关项目指令、测试和错误证据。Bug 先复现或找到可追溯的失败路径，再解释原因和最小修复。
明确请求是审查还是修改：只要求 review 时给发现，不自动修复；要求整理、修复时直接执行。可推断的命名、目录和实现细节自行决定。
按风险选择工作量
- 小范围重命名、删重复、文案或注释调整：直接修改并检查 diff，不强制计划卡或新增测试。
- 行为修改：从输入、状态变化到输出追踪一条业务路径，覆盖本次缺陷与相关失败条件；复用已有测试。
- 跨模块重构、迁移或多项验收：用简短诊断记录说明原因、影响范围、接口约束和验证方案。需要时参考 review checklist。
公共接口变化若已在用户要求内，继续实现兼容或迁移方案；只有会超出约定范围、损失用户数据或破坏他人工作且无法隔离时才需要决定。请求确认之前先完成不依赖该决定的工作。
修改与验证
沿用现有组件和依赖。修复真正拥有逻辑的模块；更新因本次行为变化失效的文档、命令或示例，不写无关历史说明。
每个行为修改保留“需求 → 修改 → 验证”的证据，可以是一段说明，不强制表格。按影响运行针对性测试、类型检查或构建；UI 行为需要真实交互证据。通过必需检查后即交付，只有新改动、失败或未解假设才扩大检查。
测试应能发现实际回归，不为可逆的小改动编写重复实现的测试。不因工具缺失冒充通过：报告失败命令、原因及仍未验证的行为。
交付
说明改了什么、原因、实际验证和剩余阻塞。Bug 修复补一句如何避免再次发生。审查以有证据的发现及文件位置开头。
只请求本地整理时不扩大为发布。若用户已要求“整理后提交/推送”，本地验证完成后继续 $cs-ending-time，沿用已有授权；若用户明确“确认后再提交”，在该处停下。
What ships with it
2 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.
- 19d ago Changed · -73 lines · -74 tokens per session c1417f7e55b0
- 1mo ago First seen · 112 lines · 128 tokens per session scan A f269674a652e
cs-clean-code is a skill published in the GitHub repository ChenShuo2004/cs-skills (204 stars, last pushed 18d ago), licensed MIT. It adds 54 tokens to every session and 655 once invoked, about $0.0002 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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…