verify-before-claiming

verify-before-claiming is a cursor rule for Cursor from the-hooman-loop/anti-slop-kit. It costs 116 tokens per session, scanned A, original, MIT.

A set of rules that requires checking work before declaring it complete.

In plain words
What is it for?
It helps verify tests, builds, running applications, user interfaces, links, calculations, and data, while reporting what was and was not checked.
Why use it?
It prevents confident claims about code or changes that have not actually been tested or inspected.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit It helps verify tests, builds, running applications, user interfaces, links, calculations, and data, while reporting what was and was not checked.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/the-hooman-loop/anti-slop-kit/verify-before-claiming
Install

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.

Clone the repo
git clone --depth 1 https://github.com/the-hooman-loop/anti-slop-kit

Made for: Cursor.

Wrote 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.

agentmods badge for verify-before-claiming

README.md
[![agentmods](https://agentmods.dev/badge/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming/github.svg)](https://agentmods.dev/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming)
Your own site
<a href="https://agentmods.dev/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming"><img src="https://agentmods.dev/badge/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming/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.

agentmods 80×15 button for verify-before-claiming

Your own site · 80×15
<a href="https://agentmods.dev/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming"><img src="https://agentmods.dev/badge/rules/the-hooman-loop/anti-slop-kit/verify-before-claiming.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 This file is loaded in full into every session.
When invoked 116 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00116 $0.00116
Opus 5 $0.00058 $0.00058
Sonnet 5 $0.00023 $0.00023
Haiku 4.5 $0.00012 $0.00012

Measured 8d ago against content hash 5b8715c4c2b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

verify-before-claiming 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 8d 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.

adapters/cursor/rules/verify-before-claiming.mdc · 21 lines

What it actually says

Do not claim that work is complete unless it has been verified.

When possible:

  • Run the relevant tests.
  • Run the app or build.
  • Check the UI manually.
  • Verify links, calculations, and data.
  • Report the actual command or check that was run.

If verification was not possible, say what was not verified and why.

Never replace real verification with a confident-sounding summary.

Fuller version: skills/verify/SKILL.md in the anti-slop-kit.

Changes

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.

  1. 8d ago First seen · 21 lines · 116 tokens per session scan A 5b8715c4c2b9

Subscribe to this mod's changes

verify-before-claiming is a cursor rule published in the GitHub repository the-hooman-loop/anti-slop-kit (4 stars, last pushed 15d ago), licensed MIT. It adds 116 tokens to every session, about $0.0006 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.