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/plan)<a href="https://agentmods.dev/rules/wellapp-ai/well/plan"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/plan/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/plan"><img src="https://agentmods.dev/badge/rules/wellapp-ai/well/plan.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.03116 |
| Opus 5.5 | $0.00003 | $0.01246 |
| Sonnet 5.5 | $0.00002 | $0.00623 |
| Haiku 4.5 | $0.00001 | $0.00312 |
Grade A, and why
plan 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Mode (Value Engineering)
Transform the QA Contract from Value Analysis into an actionable Commit Plan with technical decisions.
┌─────────────────────────────────────────────────────────────┐
│ PHASE 1: APPETITE │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ Scope │ → │ Risk │ │
│ │ Flexibility │ │ Tolerance │ │
│ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 2: REUSE INVENTORY (CRITICAL) │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Search │ → │ Document │ → │ Validate │ │
│ │ Codebase │ │ Assets │ │ Reuse │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 3: TECHNICAL DIVERGE │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Invoke │ → │ Score │ → │ Gate 3? │ │
│ │tech-diverge │ │ (0-8) │ │ (if >= 4) │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ (KO → decision-capture)│
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 4: COMMIT PLAN │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Define │ → │ Map │ → │ Estimate │ │
│ │ Commits │ │ Satisfies │ │ LOC/Time │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────┐
│ PHASE 5: THRESHOLD PROJECTION │
│ ┌─────────────┐ ┌─────────────┐ │
│ │ Predict │ → │ Identify │ │
│ │ PR Trigger │ │ PR Scope │ │
│ └─────────────┘ └─────────────┘ │
└─────────────────────────────────────────────────────────────┘
↓
Agent Mode (Value Delivery)
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 · 396 lines · 8 tokens per session scan A fd01fa9cfd08
plan 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 3,116 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
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
test-running
When running tests, use the --watch false flag to avoid watch mode.
windsurfrules
Create detailed components with these requirements.
middleware
When you need create a middleware to protect some page of Next.js app.
memory
Establishes a persistent memory protocol for capturing and retrieving knowledge, including storage strategies, context retrieval, and proactive memory management for continuous learning.
v5
Foundation rules for coding assistance. Defines task classification (lightweight/standard/critical), tool usage policies, and response style.