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 phuonghx/aim-cli --skill clean-codegit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/clean-code)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/clean-code"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/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/phuonghx/aim-cli/clean-code"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/clean-code.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.00064 | $0.01125 |
| Opus 5.5 | $0.00026 | $0.00450 |
| Sonnet 5.5 | $0.00013 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00112 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pragmatic Coding Standards
The aim is working software written plainly. Be concise, be direct, and solve the actual problem — nothing more.
Guiding Principles
- One job per unit — a function or class should do a single thing.
- No duplication — when logic repeats, lift it out and share it.
- Simplest thing that works — favor the obvious solution over the clever one.
- Build only what's needed — skip features no one asked for yet.
- Leave it tidier — every file you touch should come out a little cleaner.
Naming
| Thing | Convention | Good |
|---|---|---|
| Variables | Say what they hold | retryCount, not n |
| Functions | Action + subject | fetchOrder(), not order() |
| Booleans | Phrase as a yes/no | isReady, hasAccess, canDelete |
| Constants | Upper snake case | DEFAULT_TIMEOUT_MS |
If a name needs a comment to be understood, the name is wrong — rename it.
Functions
- Short — aim for 5–10 lines, treat 20 as a ceiling.
- Focused — one responsibility, done well.
- Single altitude — don't mix high-level orchestration with low-level detail in the same body.
- Lean signatures — zero to two parameters ideally, three at most.
- No surprise mutations — don't quietly alter the caller's data.
Structure
- Use guard clauses to handle edge cases up front and return early.
- Keep nesting shallow — two levels deep is plenty.
- Prefer small pieces composed together over one sprawling block.
- Keep related code physically close.
How to Respond While Coding
- Feature requested → write it, skip the preamble.
- Bug reported → fix it; don't narrate the fix.
- Requirement unclear → ask, rather than guessing.
Anti-Patterns to Avoid
| Don't | Do instead |
|---|---|
| Annotate every line | Drop comments that restate the code |
| Wrap a one-liner in a helper | Inline it |
| Build a factory for two cases | Construct them directly |
Create utils.ts for a lone function |
Put it where it's used |
| Open with "First we import…" | Just write the code |
| Nest four levels deep | Flatten with guard clauses |
| Sprinkle magic numbers | Name the constant |
| Write a 200-line god function | Split it by responsibility |
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 · 146 lines · 64 tokens per session scan A 3294ea82f235
clean-code is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,125 once invoked, about $0.0003 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
memory-retain
Save what was learned to Hindsight long-term memory. Use when a task finishes, when the user states a fact, decision or preference, and when you discover something a later run or another Bot would need.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…
doc-coauthoring
Collaboratively author technical specifications, RFCs, PRDs, ADRs, and decision documents through structured context gathering, iterative refinement, and blind reader testing. Use when drafting substantial documentation, architecture proposals, or engineering design records.