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 cz1993/vibe-coding-repository-standard --skill repository-hygienegit clone --depth 1 https://github.com/cz1993/vibe-coding-repository-standardWrote 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/cz1993/vibe-coding-repository-standard/repository-hygiene)<a href="https://agentmods.dev/skills/cz1993/vibe-coding-repository-standard/repository-hygiene"><img src="https://agentmods.dev/badge/skills/cz1993/vibe-coding-repository-standard/repository-hygiene/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/cz1993/vibe-coding-repository-standard/repository-hygiene"><img src="https://agentmods.dev/badge/skills/cz1993/vibe-coding-repository-standard/repository-hygiene.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.00052 | $0.00368 |
| Opus 5 | $0.00026 | $0.00184 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
repository-hygiene 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 12d 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
Repository Hygiene Audit
Inputs
- repository root;
- audit scope;
- approved standard version;
- known production/scheduler/operator context, if safely available.
Constraints
- Read-only by default.
- Do not access production or client data.
- Do not delete, move, rename, refactor, upgrade, or rewrite during the audit.
- Do not treat missing static references as proof of no external caller.
- Do not optimize for file-count reduction.
Procedure
- Inventory documentation, agent instructions, skills, custom agents, hooks, memory, MCP, scripts, generated output, tests, CI, deployment, and entry points.
- For candidate stale items, check imports/callers, CLI registration, scheduler/CI, deployment/IaC, runbooks, operators, external integrations, and data/file side effects.
- Classify each item:
- keep;
- merge;
- move to an authoritative location;
- generated;
- superseded and safe to delete;
- retention/archive required;
- unknown and investigate.
- Identify rules better enforced by tests/CI.
- Identify context duplication and instruction precedence problems.
- Produce a risk-ranked proposal with evidence and validation steps.
Output
- inventory and classification;
- evidence for proposed removals;
- contradictions and unknowns;
- proposed small cleanup changesets;
- rules to convert into executable controls;
- expected context/maintenance improvement;
- items deliberately retained.
Deletion and refactoring require a separate reviewed change.
What ships with it
1 file 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.
- 12d ago First seen · 50 lines · 52 tokens per session scan A 6998a7ef2a62
repository-hygiene is a skill published in the GitHub repository cz1993/vibe-coding-repository-standard (21 stars, last pushed 27d ago), licensed Apache-2.0. It adds 52 tokens to every session and 368 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-30.
Other skills, from other repositories
scoped-change
Judgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag…
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…
hooksmith
Use when designing or reviewing safe Grok Build hooks for linting, tests, formatting, notifications, command guards, lifecycle automation, or project hook trust decisions.
repo-health-check
Use when auditing a repo before changes to find the smallest safe PR, quality risks, stale docs, missing tests, ignored-file gaps, or agent setup issues. Best first skill for unfamiliar codebases.
architecture-review
Use for clean architecture, modular monoliths, hexagonal boundaries, service boundaries, data flow, dependency direction, ADRs, or large feature planning.
frontend-ux-engineer
Use for frontend features, Next.js/React/Vue/Svelte UI, accessibility, responsive layout, design polish, state handling, forms, visual QA, or product workflow improvements.