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 skills add bhumik154/claim-check --skill honest-test-claimsgit clone --depth 1 https://github.com/bhumik154/claim-checkWrote 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/skills/bhumik154/claim-check/honest-test-claims)<a href="https://agentmods.dev/skills/bhumik154/claim-check/honest-test-claims"><img src="https://agentmods.dev/badge/skills/bhumik154/claim-check/honest-test-claims/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/skills/bhumik154/claim-check/honest-test-claims"><img src="https://agentmods.dev/badge/skills/bhumik154/claim-check/honest-test-claims.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.00085 | $0.00626 |
| Opus 5 | $0.00043 | $0.00313 |
| Sonnet 5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00063 |
Grade A, and why
honest-test-claims 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Honest test claims
The rule
Never state a test count you did not read from actual output in this session.
If you are about to write "22 passed", "15/17 passing", "all tests pass", or "the suite is green", the number must come from a test run whose output you actually saw. Not from memory of an earlier run, not from the number of tests you believe you wrote, not from a count that was true before your last edit.
If you have not seen the output, you have two honest options:
- Run the suite, read the summary line, and state that number.
- Say what you actually know: "I added 3 tests; I have not run the suite."
Both are fine. Inventing the number is not.
Why this is a real failure mode, not a hypothetical
Test counts drift constantly during a session. A fix lands, a test splits, a parametrize gains a case, and a number that was true ten minutes ago is now wrong. Restating it from memory feels like reporting and is actually guessing.
The specific trap: a count you stated earlier in the session is evidence to you that the count is right, because you remember asserting it confidently. It is not evidence. It is your own earlier claim.
What counts as having seen the output
The pytest summary line, verbatim, from a run in this session:
=========== 1 failed, 21 passed in 0.09s ===========
That line is authoritative. Do not re-derive a total by counting individual
PASSED lines, and do not adjust a previous run's number in your head to
account for edits you made since, rerun instead.
Scope matters as much as the number
pytest -k something and pytest tests/unit/ produce real, correct summary
lines for a subset. Quoting one of those as "all tests pass" is wrong even
though the number is accurate, because the claim is about a scope the run did
not cover.
State the scope when it is not the whole suite: "22 passed in tests/unit"
rather than "22 passed".
What this skill does not ask
It does not ask you to run the test suite before finishing every task. If you are not making a claim about test results, there is nothing here to satisfy. Say nothing about counts and this skill is irrelevant.
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.
- 11d ago First seen · 64 lines · 85 tokens per session scan A d738f5107ab1
honest-test-claims is a skill published in the GitHub repository bhumik154/claim-check (2 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 626 once invoked, about $0.0004 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 skills, from other repositories
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.
bun-test-lifecycle
Use for test lifecycle hooks: beforeAll, afterAll, beforeEach, afterEach, fixtures, preload.
bun-test-mocking
Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.
api-contract-testing
Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.