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 ALTEN-group/coding-pal --skill hypothesis-ledgergit clone --depth 1 https://github.com/ALTEN-group/coding-palWrote 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/alten-group/coding-pal/hypothesis-ledger)<a href="https://agentmods.dev/skills/alten-group/coding-pal/hypothesis-ledger"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/hypothesis-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.
<a href="https://agentmods.dev/skills/alten-group/coding-pal/hypothesis-ledger"><img src="https://agentmods.dev/badge/skills/alten-group/coding-pal/hypothesis-ledger.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.00090 | $0.00782 |
| Opus 5.5 | $0.00036 | $0.00313 |
| Sonnet 5.5 | $0.00018 | $0.00156 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
hypothesis-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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hypothesis Ledger
Keep a ledger of every outcome bet and review it after its watch window. The script computes a proposed verdict with its maths. It never writes a verdict: the Product Owner decides, and an invalidated feature is deleted.
When to Use This Skill
- A backlog issue names an outcome metric and the work item ships: add an
Openrow. - The weekly Outcome review needs the hypotheses due for a verdict and the invalidated features still waiting for deletion.
- Someone has the observed metric and wants the proposed verdict with its maths before the review.
- CI validates
specs/learn/hypotheses.mdon a pull request. - The monthly retrospective needs the hypothesis validation rate and the feature deletion rate.
Path resolution
Resolve references/ and scripts/ relative to this skill's install directory (the folder that contains this SKILL.md), not the consumer repository root or the current shell cwd. If the skill was installed under .agents/skills/hypothesis-ledger/ or .claude/skills/hypothesis-ledger/, use that base path.
Workflow
- Read
references/hypothesis-ledger-contract.mdnow. It is the authoritative source for columns, verdicts, actions, and the proposal maths. - Register a hypothesis when the work item ships (the row starts
Open):
node scripts/ledger.mjs add --file specs/learn/hypotheses.md --issue 42 \
--hypothesis "Order templates shorten order entry" --metric "Minutes per order" \
--baseline 6 --target 3 --direction down --watch-ends 2026-11-30
- Before the Outcome review, list what is due and propose verdicts from the observed numbers:
node scripts/ledger.mjs due --file specs/learn/hypotheses.md --today 2026-12-01
node scripts/ledger.mjs propose --file specs/learn/hypotheses.md --issue 42 --observed 3.4
node scripts/ledger.mjs stats --file specs/learn/hypotheses.md
- Present each proposed verdict with its maths and suggested actions. Do not edit the
Verdict,Action, orDecidedcells. The Product Owner records them, as<name> (Product Owner) on YYYY-MM-DD, in a pull request. - Validate the ledger after every human edit and in CI:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 58 lines · 90 tokens per session scan A 8275cdbd51aa
hypothesis-ledger is a skill published in the GitHub repository ALTEN-group/coding-pal (5 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 782 once invoked, about $0.0004 per session on Opus 5.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-10-14.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.