Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add RandyNorthrup/high-quality-projects-skill/plugin install high-quality-projects-skillWrote 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/randynorthrup/high-quality-projects-skill/quality_retrofit)<a href="https://agentmods.dev/skills/randynorthrup/high-quality-projects-skill/quality_retrofit"><img src="https://agentmods.dev/badge/skills/randynorthrup/high-quality-projects-skill/quality_retrofit/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/randynorthrup/high-quality-projects-skill/quality_retrofit"><img src="https://agentmods.dev/badge/skills/randynorthrup/high-quality-projects-skill/quality_retrofit.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.00132 | $0.05325 |
| Opus 5 | $0.00066 | $0.02662 |
| Sonnet 5 | $0.00026 | $0.01065 |
| Haiku 4.5 | $0.00013 | $0.00532 |
Grade C, and why
quality_retrofit 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 2d 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.
printf '%s\n' "${PRE[@]:-}" | grep -qxF "$d" || rm -rf "$d" How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality retrofit — bring an existing codebase into compliance
Take a working codebase and raise it to strict standards without breaking it.
The hard constraint that shapes everything below: this code already works and someone depends on it. A retrofit that lands 4,000 mechanical changes in one commit is unreviewable and will be reverted. Phase the work.
Use this workflow for quality-only improvements. A requested feature or behavior
change belongs to feature_delivery; do not turn it into an unsolicited whole-
repository retrofit.
Communication style
Status updates: short, direct, no filler. Caveman style if that plugin is active. Never compress code comments, documentation, findings rationale, or risk notes.
Locating this package
Paths below use ${SKILL_ROOT}/... as a placeholder for the directory holding
this package's scripts/ and templates/. Resolve it once with the active
shell. On Windows PowerShell:
$SkillRoot = & 'C:\path\to\high-quality-projects-skill\scripts\skill-root.ps1'
On Linux, macOS, or another POSIX environment:
SKILL_ROOT="$(bash /path/to/high-quality-projects-skill/scripts/skill-root.sh)"
Both root scripts locate themselves, so they work from a plain clone, a vendored
copy, or a submodule with no environment set. They honour SKILL_ROOT, then
CLAUDE_PLUGIN_ROOT under Claude Code. Do not invoke Windows bash.exe: it can
exist as a WSL relay even when /bin/bash does not.
Nothing here is specific to one vendor. If your agent cannot run shell commands, read the files directly out of the repository — the templates are plain config files and the phases below are plain instructions.
Rule zero: scan, enhance, then create only if needed
$Scan = & "$SkillRoot\scripts\detect-stack.ps1" . | ConvertFrom-Json
Or from a POSIX shell:
"${SKILL_ROOT}/scripts/detect-stack.sh" .
Returns languages present, existing config, and installed tools. Do not change anything yet. Report:
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.
- 2d ago Changed · +49 lines f2a46d981965
- 10d ago First seen · 447 lines · 132 tokens per session scan C b79bd9490458
quality_retrofit is a skill published in the GitHub repository RandyNorthrup/high-quality-projects-skill (1 stars, last pushed 2d ago), licensed MIT. It adds 132 tokens to every session and 5,325 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
procoder
Work like a senior developer in a repository governed by procoder: run the commit gate before calling anything done, format and lint through the binary, and drive the spec, plan, todo, backlog, and sprint chain in .procoder/. Use this skill when the repository contains a .procoder/ directory or an AGENTS.md naming…
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
brooks-audit
Architecture audit that maps module dependencies, checks layering integrity, and flags structural decay across a codebase, drawing on twelve classic engineering books. Triggers when: user asks to audit architecture, review folder/module structure, check for circular imports, understand how the codebase is organized…
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…
brooks-test
Test quality review drawing on twelve classic engineering books — with primary focus on xUnit Test Patterns, The Art of Unit Testing, How Google Tests Software, and Working Effectively with Legacy Code — that diagnoses structural problems in an existing test suite: brittleness, mock abuse, coverage illusions, slow…