Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add slbug/claude-ruby-grape-rails/plugin install ruby-grape-railsWrote 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/slbug/claude-ruby-grape-rails/provenance-scan)<a href="https://agentmods.dev/skills/slbug/claude-ruby-grape-rails/provenance-scan"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/provenance-scan/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/slbug/claude-ruby-grape-rails/provenance-scan"><img src="https://agentmods.dev/badge/skills/slbug/claude-ruby-grape-rails/provenance-scan.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.00064 | $0.01061 |
| Opus 5.5 | $0.00026 | $0.00424 |
| Sonnet 5.5 | $0.00013 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
rb:provenance-scan 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 1mo 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provenance Scan
Self-audit for the project's research and review provenance sidecars.
Outputs a per-state count plus a per-file list so the user can decide
whether upcoming /rb:plan --existing, /rb:work, or /rb:review
runs are relying on solid evidence or single-source claims.
Schema reference:
${CLAUDE_PLUGIN_ROOT}/references/output-verification/trust-states.md${CLAUDE_PLUGIN_ROOT}/references/output-verification/provenance-template.md
Iron Laws
- Never invent or edit claims, sources, or conflicts to change a
state. A
weak/missingstate is a diagnostic; rewriting the sidecar to silence it defeats every workflow that readstrust_state. If a state is wrong, fix the underlying research, not the sidecar. - Never auto-fix sidecars. Remediation belongs to the producing
skill (
/rb:research,/rb:review). This skill reports only. - Never re-use a stale report. If any
*.provenance.mdchanged since the last run, re-run the scan before acting on it. - Read only the sidecar frontmatter, not the raw artifact alongside
each
.provenance.md. The scan reports on evidence shape, not on the artifact's content. Pulling the raw body into the report bloats it without changing the trust-state classification, and any subsequent modify-the-artifact follow-up is out of scope (Iron Law #2 covers auto-fix prohibition). weakis not a blocker;conflictedis. Onlyconflictedshould halt a downstream/rb:plan --existingor/rb:workstep.weakandmissingwarn but proceed.
How to run
${CLAUDE_PLUGIN_ROOT}/bin/provenance-scan
Optional --root PATH points at a project other than the current
directory. Exit code is 0 whether the distribution is all-clean or
all-conflicted — the report file is the contract, not the exit code.
Where it looks
.claude/research/**/*.provenance.md.claude/reviews/**/*.provenance.md.claude/audit/**/*.provenance.md.claude/plans/<slug>/{research,reviews}/**/*.provenance.md
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.
- 1mo ago First seen · 103 lines · 64 tokens per session scan A ea6615aa56ba
rb:provenance-scan is a skill published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 16d ago), licensed MIT. It adds 64 tokens to every session and 1,061 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
omh-rust
This is an OMH rust workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.