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/paladini/harness-score/coregit clone --depth 1 https://github.com/paladini/harness-scoreWhat 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.00245 | $0.00245 |
| Opus 5 | $0.00122 | $0.00122 |
| Sonnet 5 | $0.00049 | $0.00049 |
| Haiku 4.5 | $0.00024 | $0.00024 |
Grade A, and why
core 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 2d 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
- The scanner is deterministic by contract: no model calls, no network, no time-dependent output. If a proposed check needs judgment, it does not belong in the CLI — it belongs in the guide as advice.
packages/clihas zero runtime dependencies. Do not add one.- Check changes touch three files together:
packages/cli/src/score.ts,docs/guide/maturity-model.md,docs/guide/measure-and-improve.md— enforced in CI bydocs.test.tsandmaturity-sync.test.ts. - Guide edits must keep all five locales in sync — see
.cursor/rules/docs-i18n-parity.mdcanddocs.test.ts(file set + anchor parity). - Check IDs are stable public API (they are documentation anchors and appear in users' CI logs). Never renumber, reuse, or delete an ID — deprecate by making the check always-pass if truly needed.
- This repository must keep scoring L4 on
npm run scan.
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.
- 2d ago First seen · 19 lines · 245 tokens per session scan A 7f0939d8b912
core is a cursor rule published in the GitHub repository paladini/harness-score (199 stars, last pushed 4d ago), licensed MIT. It adds 245 tokens to every session, about $0.0012 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
project
Project conventions - canonical source is AGENTS.md.
frontend
UI/component conventions. Apply when building or changing user-facing frontend code.
core
The engineering contract for this repo lives in AGENTS.md (auto-loaded). Follow it. This rule only adds Cursor-specific behavior so the contract is not duplicated token-for-token on every request.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
no-auto-commit
Never commit or push without explicit user instruction.
wallet-transaction-safety
IronWallet transfers and swaps — hot wallet, no blind retries.