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 rules/randynorthrup/high-quality-projects-skill/high-quality-projectsgit clone --depth 1 https://github.com/RandyNorthrup/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/rules/randynorthrup/high-quality-projects-skill/high-quality-projects)<a href="https://agentmods.dev/rules/randynorthrup/high-quality-projects-skill/high-quality-projects"><img src="https://agentmods.dev/badge/rules/randynorthrup/high-quality-projects-skill/high-quality-projects.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00220 |
| Opus 5 | $0.00004 | $0.00110 |
| Sonnet 5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
high-quality-projects 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 4d 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
This repository provides two workflows for applying production-oriented code standards. Both are plain Markdown and can be followed outside Cursor.
- New project → read
skills/project_setup/SKILL.md - Existing codebase → read
skills/quality_retrofit/SKILL.md
Read the whole file before acting. Both open with a mandatory read-only scan
(scripts/detect-stack.ps1 on PowerShell or scripts/detect-stack.sh on
POSIX) that must run before anything is created or changed.
Paths inside those files use ${SKILL_ROOT}/... as a placeholder. On
PowerShell, resolve with:
$SkillRoot = & '.\scripts\skill-root.ps1'
On POSIX, resolve with:
SKILL_ROOT="$(bash scripts/skill-root.sh)"
Full detail, including the non-negotiable rules, is in AGENTS.md at the
repository root.
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.
- 4d ago First seen · 31 lines · 8 tokens per session scan A d31502a889ee
high-quality-projects is a cursor rule published in the GitHub repository RandyNorthrup/high-quality-projects-skill (1 stars, last pushed 12d ago), licensed MIT. It adds 8 tokens to every session and 220 once invoked, about $0.0000 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 cursor rules, from other repositories
procoder
You are working in a repository governed by Procoder — a harness that gives AI coders the tools and discipline of a senior developer. The procoder binary computes; you act. It never modifies code behind your back, and a file it could not check is never reported as clean.
slopmop-init
Slop-mop initial project setup — bootstrap a repo that has sm installed but no .sbconfig.json.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.