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.
git clone --depth 1 https://github.com/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/repo-health)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/repo-health"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/repo-health/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/rules/thatrebeccarae/claude-marketing/repo-health"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/repo-health.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.00039 | $0.02391 |
| Opus 5 | $0.00019 | $0.01196 |
| Sonnet 5 | $0.00008 | $0.00478 |
| Haiku 4.5 | $0.00004 | $0.00239 |
Grade A, and why
repo-health 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 13d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Health
One-command health audit for GitHub repositories. Produces a scored report with prioritized fix recommendations.
When to Use
- Setting up a new repo and want to make sure nothing is missing
- Periodic health checks on active repositories
- Before open-sourcing a private repo (what needs to be added?)
- Onboarding onto an unfamiliar repo to assess its state
- Pre-release hygiene sweep
How to Use
/repo-health [repo-path] # Full audit with scored report
/repo-health [repo-path] --fix # Audit + generate missing files
Default repo-path is the current working directory if omitted.
Procedure
Execute each step in order. Do not skip steps.
Step 1: Validate Repo Path
- If
repo-pathis provided, resolve to absolute path. If omitted, use current working directory. - Confirm the path exists and is a directory.
- Confirm it contains a
.gitdirectory (is a git repo).
If validation fails:
Error: {repo-path} is not a git repository.
Provide a path to a git repo or run from within one.
STOP.
Step 2: Detect Public/Private
Determine repo visibility:
- Check for
.public-repomarker file at repo root -> public - Check if "public" appears in the remote URL -> public
- Run
gh repo view --json isPrivate -q '.isPrivate'ifghis available -> use result - If none of the above resolve it -> ask the user
Store as repo_visibility (public or private). Public repos are held to a stricter standard in scoring.
Step 3: File Presence Checks
Check for each standard file. Track result as PRESENT or MISSING.
| File | Required (Public) | Required (Private) |
|---|---|---|
LICENSE |
Yes | No |
README.md |
Yes | Yes |
.gitignore |
Yes | Yes |
SECURITY.md |
Yes | No |
CONTRIBUTING.md |
Yes | No |
CODEOWNERS |
Recommended | No |
.editorconfig |
Recommended | Recommended |
.github/pull_request_template.md or .github/PULL_REQUEST_TEMPLATE.md |
Recommended | No |
.github/ISSUE_TEMPLATE/ directory (or .github/ISSUE_TEMPLATE.md) |
Recommended | No |
CHANGELOG.md |
Recommended | No |
CODE_OF_CONDUCT.md |
Recommended (public) | No |
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.
- 13d ago First seen · 254 lines · 39 tokens per session scan A 0c173f95dc6e
repo-health is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (137 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 2,391 once invoked, about $0.0002 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.