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 agentmods add skills/kouroshez/coding-os/clean-codenpx skills add kouroshez/coding-os --skill clean-codegit clone --depth 1 https://github.com/kouroshez/coding-osWhat 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 | $0.00065 | $0.10467 |
| Opus 5 | $0.00032 | $0.05234 |
| Sonnet 5 | $0.00013 | $0.02093 |
| Haiku 4.5 | $0.00006 | $0.01047 |
Grade A, and why
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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill enforces universal coding principles on every code change. It is stack-agnostic — same rules hold for Python backends, TypeScript frontends, Go services, and any other language the project uses. Stack-specific layering (Django ORM, FastAPI dependencies, Fiber middleware, React hooks) lives in the matching stack skill that depends on this one.
Read the why, not just the diff. Every rule below pairs the wrong shape (
BAD) with the right one (GOOD) and the reason the right one is right — and the reason is the point. Internalize it and you apply the principle where no rule is written (the out-of-distribution case that no linter catches); copy theGOODdiff alone and you only pass the cases someone already enumerated. These tactics are the concrete expression of the project's constitution values — smallest-correct-change, docs-are-the-contract, agent-agnostic — which carry the WHY one level up. (This is the Teaching Claude Why finding applied to ourselves: a principle understood generalizes; a demonstration copied does not.)
Strategic parent: This skill enforces the tactical shape of code (naming, structure, error paths). The strategic anti-overengineering rule — reuse first, no speculation, diff-minimal, rule-of-three abstraction — lives in src/core/rules/anti-overengineering.md and applies to every artifact (docs, hooks, skills, templates, tests, CLI), not just code. Read it before introducing a new abstraction.
Pre-Code Checklist
Before writing any code, verify you have read the relevant context:
- Read the engineering doc for the surface being changed (each stack ships its own under
docs/engineering/<stack>-rules.md,docs/engineering/frontend-rendering-rules.md, or the meta-repo'sdocs/architecture/meta-project.md). - If touching error handling or API responses: read api-contract-discipline.md and the project's error-envelope doc (
docs/engineering/mcp-error-envelope.mdforcos_*MCP tools,docs/api-contracts/error-format.mdfor HTTP services). - If touching auth, payments, or file uploads: read
docs/playbooks/security-review.md. - Search the repo for existing patterns before introducing new ones — see the search skill for the grounded-count workflow.
- Before adding code to a service subtree in a polyglot project, confirm placement against the
docs/engineering/project-anatomy.mdSSOT: same-language reuse lives insrc/shared/<lang>/, cross-language types insrc/shared/contracts/— see §7.
What ships with it
5 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.
- yesterday First seen · 587 lines · 65 tokens per session scan A 01514a8b9574
clean-code is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 10,467 once invoked, about $0.0003 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
potpie-infra-architecture
Use for project infra and architecture context: environments, adapters, runtime configuration, deployments, service dependencies, datastores, API contracts, ownership, incidents, and dependency blast radius.
wiki-context-pack
Produce a token-bounded, citation-ready context slice from an existing Obsidian vault for a downstream agent or task. Use for "/wiki-context-pack", "use my vault as context", "context slice for X", "pack the wiki for my agent", or "bounded context for Y".
alfworld-receptacle-finder
Searches for a suitable empty or appropriately occupied receptacle (like a shelf or table) to place an object. Use when you are holding an object that needs to be stored or placed and must find a receptacle that meets the placement criteria. Examines candidate receptacles by navigating to and inspecting each one until…
alfworld-search-pattern-executor
Systematically searches a sequence of likely locations for a target object based on common sense. Use when you need to find a specific object and know which receptacles to check but not which one contains it. Takes a list of candidate receptacles, orchestrates navigation and inspection, and outputs when the target is…
ux-ui-analyze-single-page
Analyze exactly one captured UI page (from uxuimap screenshots + request JSON) and immediately write/update uxuimap/pages/{page}.md in neutral descriptive language. Use when asked to analyze screenshots, rewrite corresponding analysis immediately, or avoid memory/context saturation.