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/tatemz/habitica-mcpWrote 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/tatemz/habitica-mcp/deterministic-delivery)<a href="https://agentmods.dev/rules/tatemz/habitica-mcp/deterministic-delivery"><img src="https://agentmods.dev/badge/rules/tatemz/habitica-mcp/deterministic-delivery.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.1 | $0.00321 | $0.00321 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00064 | $0.00064 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
deterministic-delivery 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 7d 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
Deterministic Delivery
This repo optimizes for reproducible behavior over speed theatre.
Rules:
- Use
pnpm;packageManageris pinned and policy-checked. - Run the smallest relevant check first, then widen only when risk justifies it.
- Keep
pnpm checkas the merge gate. Do not weaken it to get green. - Generated artifacts stay out of git:
dist/,coverage/,reports/,.stryker-tmp/, andnode_modules/. - Every non-trivial behavior change gets one runnable check that fails if the behavior regresses.
- Deterministic policy scripts should read structured files when practical; avoid shelling out for parsing.
- If a rule is bad, delete or replace it with a specific reason. Do not add broad suppressions.
- Coverage and mutation scope is all of
src/**/*.ts. Narrow it only through a named exception inscripts/policy-exceptions.tswith a rationale and a removal condition. - Never add a suppression comment. There is no
oxlint-disable,@ts-ignore, orStryker disablepath; fix the code instead. - Lower
policy/mutation-baselines.jsononly when a refactor genuinely removes mutants, and record why in itsrationale. - Assert exact values in tests. No
toBeDefined/toBeTruthy/toBeFalsy, and no baretoThrow().
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.
- 7d ago First seen · 23 lines · 321 tokens per session scan A dd35e1a29220
deterministic-delivery is a cursor rule published in the GitHub repository tatemz/habitica-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 321 tokens to every session, about $0.0016 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
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.