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/wellapp-ai/well/agentgit clone --depth 1 https://github.com/WellApp-ai/WellWhat 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.02187 |
| Opus 5 | $0.00004 | $0.01094 |
| Sonnet 5 | $0.00002 | $0.00437 |
| Haiku 4.5 | $0.00001 | $0.00219 |
Grade A, and why
agent 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 yesterday.
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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Mode (Value Delivery)
Execute the Commit Plan from Value Engineering, with per-commit verification and threshold-based PR triggers.
Commit-Level Workflow
┌─────────────────────────────────────────────────────────────┐
│ For each commit in Commit Plan: │
│ │
│ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │
│ │ Implement │ → │ pr-review │ → │ qa-commit │ │
│ │ Changes │ │ skill │ │ skill │ │
│ └─────────────┘ └─────────────┘ └─────────────┘ │
│ │ │ │ │
│ │ │ ┌──────┴──────┐ │
│ │ │ │ │ │
│ │ │ GREEN RED │
│ │ │ │ │ │
│ │ │ ▼ ▼ │
│ │ │ ┌───────────┐ ┌───────────┐ │
│ │ │ │Git Commit │ │ debug │ │
│ │ │ └───────────┘ │ skill │ │
│ │ │ │ └───────────┘ │
│ │ │ │ │ │
│ │ │ ▼ │ │
│ │ │ ┌───────────┐ │ │
│ │ │ │pr-threshold│◄──────┘ │
│ │ │ │ skill │ │
│ │ │ └───────────┘ │
│ │ │ │ │
│ │ │ ┌──────┴──────┐ │
│ │ │ │ │ │
│ │ │ CONTINUE TRIGGER_PR │
│ │ │ │ │ │
│ │ │ ▼ ▼ │
│ │ │ Next push-pr │
│ │ │ Commit mode │
│ │ │ │
└─────────────────────────────────────────────────────────────┘
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.
- yesterday First seen · 348 lines · 8 tokens per session scan A ee3c608f8037
agent is a cursor rule published in the GitHub repository WellApp-ai/Well (341 stars, last pushed 25d ago), licensed MIT. It adds 8 tokens to every session and 2,187 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-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.
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.
taskmaster
Comprehensive reference for Taskmaster MCP tools and CLI commands.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.