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 simiancraft/simiancraft-skills --skill prove-work-on-githubgit clone --depth 1 https://github.com/simiancraft/simiancraft-skillsWrote 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/simiancraft/simiancraft-skills/prove-work-on-github)<a href="https://agentmods.dev/skills/simiancraft/simiancraft-skills/prove-work-on-github"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/prove-work-on-github/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/simiancraft/simiancraft-skills/prove-work-on-github"><img src="https://agentmods.dev/badge/skills/simiancraft/simiancraft-skills/prove-work-on-github.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.00175 | $0.01586 |
| Opus 5 | $0.00088 | $0.00793 |
| Sonnet 5 | $0.00035 | $0.00317 |
| Haiku 4.5 | $0.00017 | $0.00159 |
Grade A, and why
prove-work-on-github 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prove Work on GitHub
A claim is narrative; a receipt is proof. The remote is the witness, not your intent to push.
A statement about a change ("the fix works", "CI is green", "the screen looks right", "it is ready to merge") is narrative until it is paired with a receipt: verifiable evidence that you observed and that a reader can independently re-check. "I ran the command" is not "the remote advanced." A green checkmark is not "the feature is correct." This skill is the discipline that turns claims into receipts, sizes how much proof a change owes, stores the receipts durably on the pull request, and judges whether they are enough to merge.
Proof is asymptotic
Proof is never perfect; it only approaches the asymptote of perfection. The categories below are open sets, not closed enums: when you find a new signal that makes a change more provable, add it (extend your copy, or propose it upstream). The rubric ships incomplete by design and improves by contribution. A skill that claims a finished, total account of proof is lying.
When proof is owed
Proof is owed when a claim about a change would change what a reviewer or a merge gate does, and
the claim is not self-evident from the diff. Match the rigor to the change (see
references/physical.md); a typo and a schema migration do not earn the same receipt. Skip when
the diff is its own proof, or when the work never reaches GitHub.
The model: three aspects and a judgement
Three measured aspects of a change, and a judgement that interprets them. Judgement is last.
| Aspect | Question |
|---|---|
| Physical | what is the change, and how much does it therefore owe (surface area, complexity, and reversibility)? |
| Correctness | is the change sound (alignment, verifiability, durability, and security)? |
| Evidence | what receipts does that change require, by type, and at what fidelity? |
| Judgement | is the evidence adequate, and how confident are you to merge? |
Physical sizes the bar; Correctness names what must be proven; Evidence supplies the receipts; Judgement reads the three and returns an action: merge, gather more, or block.
What ships with it
10 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.
- references/acquire.md 2.6 KB
- references/artifact-manifest.md 4.5 KB
- references/catalog.md 1.5 KB
- references/correctness.md 1.6 KB
- references/evidence-locker.md 12 KB
- references/freshness-and-reproof.md 2.6 KB
- references/judgement.md 2.6 KB
- references/optimize-assets.md 2.9 KB
- references/physical.md 1.5 KB
- references/render.md 3.6 KB
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.
- 9d ago First seen · 121 lines · 175 tokens per session scan A b89dc4af3075
prove-work-on-github is a skill published in the GitHub repository simiancraft/simiancraft-skills (7 stars, last pushed 6d ago), licensed MIT. It adds 175 tokens to every session and 1,586 once invoked, about $0.0009 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
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
version-bump
This skill automates version bumping during the release process for the Claude Code Handbook monorepo. It should be used when the user requests to bump versions, prepare a release, or increment version numbers across the repository.
commit-push-pr
Full git workflow - creates branch, commits, pushes, and creates or updates a PR with summary and test plan.
commit
Create a single well-crafted git commit from current changes. Analyzes diff, follows repo's commit style, and writes a concise "why not what" message.
pr-conventions
Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…
review-pr
Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…