Install any skill in seconds. Free to start, no credit card required.
Get Started Free →karanb192/provenance
Preview the provenance receipt (prompts, est. spend, tests run, agent-authored lines) for the current session ledger
Passed 12 of 18 test cases with the skill, and 6 of 18 without it.
and 7 more in the full report
9 fixed6 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
What command-line flag is passed to pr-provenance-stamp.js to generate the preview receipt output instead of updating a PR?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the --render command-line flag. | Missed | Passed |
The instructions your model reads when the skill loads.
!node "${CLAUDE_SKILL_DIR}/../../pr-provenance-stamp.js" --render 2>/dev/null || node "${CLAUDE_PLUGIN_ROOT}/pr-provenance-stamp.js" --render
The block above is the provenance receipt exactly as it would be stamped into a PR
body when you run gh pr create, built from the most recent session ledger the
pr-provenance-stamp hook has been recording (tool calls, test/typecheck commands
with real exit codes, and the agent-vs-human authored-line split). Prompt and spend
figures come from the transcript at PR-create time, so they may be absent in this
preview.
Briefly summarize the receipt for the user: how many tests ran and whether they are green, and the agent-authored line count or percentage. Keep it to a sentence or two and do not re-run any commands.
test cases passed, vs 6 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.