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/hmj1026/dhpkWrote 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/hmj1026/dhpk/model-economics)<a href="https://agentmods.dev/rules/hmj1026/dhpk/model-economics"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/model-economics/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/hmj1026/dhpk/model-economics"><img src="https://agentmods.dev/badge/rules/hmj1026/dhpk/model-economics.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.00007 | $0.03599 |
| Opus 5.5 | $0.00003 | $0.01440 |
| Sonnet 5.5 | $0.00001 | $0.00720 |
| Haiku 4.5 | $0.00001 | $0.00360 |
Grade A, and why
model-economics 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model Economics — tier map & cost rules
SSOT for which model tier each role runs on, and the cost rules that govern tier and effort choices. The dispatch routing decision — which agent handles which work shape — lives in ${POLICY_BUNDLE_ROOT}/rules/execution-policy.md §Implementation dispatch; this file owns the cost lens over that routing and does not restate its work-shape rows. Native-vs-external candidate selection follows the shared Native dispatch baseline in execution-policy.md; model economics ranks an already-valid candidate and never enables cross-provider probing. Resource-layer markdown, opt-in — referenced from execution-policy.md §Agent dispatch (model-tier + configured-role paragraphs).
Reviewers keep a sonnet floor — no downward tiering.
reviewer_targetis the only public reviewer entry. Runtime-tunable viauserConfig: the four<role>_targetkeys (worker_target,reasoner_target,planner_target,reviewer_target, format<agent>/<model>[:<effort>]) carry model and effort for every Role, including the CLI-backedcodex-worker,codex-reasoner,codex-reviewer, andagy-worker(their model and effort come from the matching<role>_targetwhen its target Agent is that CLI; agy bakes effort into the model name). The former*_model/*_effortkeys (fast_worker_*,deep_reasoner_*,codex_fast_worker_*,codex_deep_reasoner_*,agy_fast_worker_model, and the rest) are removed keys, reportedBLOCKEDand not applied; see the configuration guide's "Removed in 0.69.0" section. Only timeouts stay role-specific:codex_worker_timeout_secs,codex_reasoner_timeout_secs,codex_reviewer_timeout_secs, with the sharedcodex_timeout_secs; budgets are integer seconds,0is an intentional dispatcher-attested no-deadline request, and malformed values fail closed. The portable runner, never a shell timeout backstop, enforces an attested nonzero deadline. The rest of the map is documentation for humans, not a runtime dial.
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 Changed · -1 tokens per session 3c5cceb82954
- 2d ago Changed · +11 lines 12bd6e7eb89c
- 12d ago Changed · +5 lines dc0ce1749f10
- 14d ago Changed · +19 lines 5e17b5401969
- 19d ago Changed a47275b882c5
- 28d ago Changed · +4 lines 411b7c05d6b6
- 1mo ago Changed · +5 lines 93691eaac894
- 1mo ago Changed 38062164be99
- 1mo ago Changed 7ad5212b2d2b
- 1mo ago First seen · 67 lines · 8 tokens per session scan A 0c2079b4864d
model-economics is a cursor rule published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 3,599 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-09-05.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.