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/WellApp-ai/WellWrote 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/wellapp-ai/well/commit)<a href="https://agentmods.dev/rules/wellapp-ai/well/commit"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/commit/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/wellapp-ai/well/commit"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/commit.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.00008 | $0.00971 |
| Opus 5.5 | $0.00003 | $0.00388 |
| Sonnet 5.5 | $0.00002 | $0.00194 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
commit 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Rules
Before committing, invoke validation skills to ensure quality.
Pre-Commit Workflow
┌─────────────────────────────────────────────────────────────┐
│ 1. Invoke pr-review skill │
│ - Runtime check (Docker, API, Web) - auto-resolve │
│ - TypeCheck, Lint, ReadLints │
│ - Risk assessment │
│ - Verdict: PASS/WARN/BLOCK │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 2. Invoke qa-commit skill │
│ - Verify Satisfies criteria (G#N, AC#N) │
│ - Verdict: GREEN/RED │
│ - If RED: Auto-invoke debug skill │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 3. Git Commit (if all pass) │
│ - Message format │
│ - Include Satisfies field │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ 4. Invoke pr-threshold skill │
│ - Check accumulated metrics │
│ - Verdict: CONTINUE/TRIGGER_PR │
└─────────────────────────────────────────────────────────────┘
Step 1: Invoke pr-review Skill
Before committing:
Invoking pr-review skill...
Required checks:
- Runtime environment ready (Docker, API:8080, Web:3000)
-
npm run typecheckpasses -
npm run lintpasses - ReadLints shows no errors on changed files
- No console.log in changed files
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 · 167 lines · 8 tokens per session scan A c438a11ff01f
commit is a cursor rule published in the GitHub repository WellApp-ai/Well (345 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 971 once invoked, about $0.0000 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-30.
Other cursor rules, from other repositories
commit-message-format
Applied when creating Git commit messages. Format rules for Conventional Commits-based Prefix + English summary + bulleted body.
git_conventions
Git-related rules and best practices for version control.
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.