bennu: Skill for Claude Code

.claude/skills/evidence-ledger/SKILL.md

evidence-ledger is a skill for Claude Code from Lengros/bennu. It costs 169 tokens per session (2,523 once invoked), scanned A, original, MIT.

A living record of the risky assumptions behind a product idea, including pre-set success or failure thresholds, experiments, evidence, and decisions.

In plain words
What is it for?
Use it to order assumptions for testing, match each one with an experiment, record evidence and its source, and decide whether to stop, change direction, or continue.
Why use it?
It prevents teams from changing their standards after seeing results and separates real evidence from curiosity or an attractive prototype.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Lengros/bennu's own configuration. It tells Claude Code how to work on bennu itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bennu configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Lengros/bennu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Lengros/bennu/main/.claude/skills/evidence-ledger/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Lengros/bennu

Made for: Claude Code.

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 evidence-ledger

README.md
[![agentmods](https://agentmods.dev/badge/skills/lengros/bennu/evidence-ledger/github.svg)](https://agentmods.dev/skills/lengros/bennu/evidence-ledger)
Your own site
<a href="https://agentmods.dev/skills/lengros/bennu/evidence-ledger"><img src="https://agentmods.dev/badge/skills/lengros/bennu/evidence-ledger/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 evidence-ledger

Your own site · 80×15
<a href="https://agentmods.dev/skills/lengros/bennu/evidence-ledger"><img src="https://agentmods.dev/badge/skills/lengros/bennu/evidence-ledger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 169 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,523 The whole file, excluding the scripts and references it only reads on demand.
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.00169 $0.02523
Opus 5 $0.00084 $0.01262
Sonnet 5 $0.00034 $0.00505
Haiku 4.5 $0.00017 $0.00252

Measured 9d ago against content hash 526b0c337e8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

evidence-ledger 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 9d 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.

.claude/skills/evidence-ledger/SKILL.md · 152 lines

How it starts

The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/evidence-ledger — living portfolio of risky assumptions

Maintains one artifact that tracks every load-bearing assumption a product bet depends on, in test order, with a threshold pre-registered before the data is seen and a forced decision after. It does not run the experiments. It keeps you honest about what each experiment can prove and stops you moving the goalposts once results arrive.

The engine, repeated at every stage: a believable surface is now free to produce, so the only thing that separates a real bet from a pretty one is a falsifiable threshold set in advance and a signal with something at stake. Curiosity is not commitment; an AI summary is not a finding; a threshold chosen after the data is rationalization.

Argument (optional): the bet/outcome, or a path to an existing ledger to update. If absent, use the bet under discussion in context.

Relationship to /reframe: /reframe regresses one request to a falsifiable outcome (the INTENT stage). /evidence-ledger sits one level up — it holds the set of assumptions behind a bet and sequences the experiments. A single assumption's experiment can itself be run through /reframe. Use reframe for "what does this task have to achieve"; use evidence-ledger for "what do we actually know about this bet, and what do we test next."


How to run

Work the seven stages in order. Append to the ledger artifact (§Schema); never rewrite a pre-registered threshold after a signal lands — supersede the row and keep the original.

  1. Frame the bet — one line: the outcome the whole ledger serves (a result in the world, not a feature). May be lifted from a prior /reframe outcome.

  2. List load-bearing assumptions — everything that must be true for the bet to pay off. State each so it can be wrong ("tutors will write up every lesson the day it happens"), not as a goal ("great onboarding"). Surface the assumptions that would kill the bet if false, not the convenient ones you already believe.

Read the full file on GitHub · 152 lines

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. 9d ago First seen · 152 lines · 0 tokens per session scan A 526b0c337e8c

Subscribe to this mod's changes

evidence-ledger is a skill published in the GitHub repository Lengros/bennu (2 stars, last pushed 2mo ago), licensed MIT. It adds 169 tokens to every session and 2,523 once invoked, about $0.0008 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.