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/paladini/harness-scoreWrote 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/paladini/harness-score/checks)<a href="https://agentmods.dev/rules/paladini/harness-score/checks"><img src="https://agentmods.dev/badge/rules/paladini/harness-score/checks/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/paladini/harness-score/checks"><img src="https://agentmods.dev/badge/rules/paladini/harness-score/checks.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.00000 | $0.00404 |
| Opus 5.5 | $0.00000 | $0.00162 |
| Sonnet 5.5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
checks 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.
What it actually says
Adding a check:
- Pick the dimension file (
context.ts,skills.ts,hooks.ts,sensors.ts,ci.ts,hygiene.ts) and the next free ID in that family's sequence (e.g.SNS-06). - A check reads ONLY through
ScanContext(has/read/matching) — neverfsdirectly, so tests can fake it. evidencemust state what was found and where, in one sentence, for both pass and fail.remediationis one actionable sentence.- Keep dimension totals in mind: a new/changed check shifts its
dimension's max, which shifts the overall total (currently 108, derived
from
ALL_CHECKS— not a number to hardcode, but a real one every maturity model change must account for). - Update the check catalog in
docs/guide/measure-and-improve.mdwith a#### <ID> · <title> — <n> pts {#<id-lowercase>}entry, and the dimension-points table + level thresholds indocs/guide/maturity-model.mdif they're affected —packages/cli/test/docs.test.tsandpackages/cli/test/maturity-sync.test.tsfail otherwise. - Add a unit test in
packages/cli/test/checks.test.ts(usefakeContext), and adjust fixtures if the check changes any fixture's expected level. - Consider opening the change as a Check change issue first (see
.github/ISSUE_TEMPLATE/check_change.yml) if it's not already agreed — this is the highest-stakes contribution surface in the repo.
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 · 31 lines · 0 tokens per session scan A b8c0a0ea6b67
checks is a cursor rule published in the GitHub repository paladini/harness-score (585 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 404 tokens. 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
prompt-to-asset
Asset generation — route, rewrite, generate, validate. Never send transparency requests to Imagen/Gemini.
swamr-orchestrator
Swamr Orchestrator — autonomous agent swarm that builds entire projects. Invoke with @swamr-orchestrator followed by what you want built. Decomposes into tasks, selects specialist agents, runs dev↔QA loops, and delivers production-ready code.
swamr-state-manager
Swamr State Manager — tracks task progress, manages the execution pipeline, handles retries and escalation. Maintains swamr/state.json as the single source of truth for swarm progress.
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
seed-phrase-handling
Never expose IronWallet recovery phrases or private keys.
monobehaviour-lifecycle
Correct usage of MonoBehaviour lifecycle methods.