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 ozzy-labs/suasor --skill provenance-tracegit clone --depth 1 https://github.com/ozzy-labs/suasorWrote 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/ozzy-labs/suasor/provenance-trace)<a href="https://agentmods.dev/skills/ozzy-labs/suasor/provenance-trace"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/provenance-trace/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/ozzy-labs/suasor/provenance-trace"><img src="https://agentmods.dev/badge/skills/ozzy-labs/suasor/provenance-trace.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.00124 | $0.00948 |
| Opus 5 | $0.00062 | $0.00474 |
| Sonnet 5 | $0.00025 | $0.00190 |
| Haiku 4.5 | $0.00012 | $0.00095 |
Grade A, and why
provenance-trace 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.
What it actually says
provenance-trace
任意の entity（task / decision / source 等）を起点に「何に由来するか」を links projection 上で辿る read-only skill（ADR-0018 / ADR-0020）。decisions（決定の「なぜ」）や find（トピック横断）に埋もれていた汎用 provenance トレースを正面から扱う。
いつ発火するか
- 「この task の出どころ」「由来を辿って」「
<entity>は何から来た」 - 「この decision の根拠 source」「provenance を遡って」「どこから派生した?」
何をするか（MCP tool flow）
read tool のみ（ADR-0004）。本文は持たず、links projection の有向エッジを辿る。
- 起点 entity を
kind+idで特定する（例task/decision/source） - provenance を辿る:
graph.related（1-hop 隣接）で直近の由来 / 関連を引く。direction（out/in/both、既定both）/relationで絞る- 多段で遡るなら
graph.expand（depth既定 2・max 10 /limit）で BFS 展開する - 後方トレース（「この成果物は何に由来するか」）は
direction=inで incoming のみを遡る（ADR-0020）。下流の consumer を見るならdirection=out
- relation は自動エッジ
derived_from/replies_to/referencesと手動エッジmanual_link（手動 link はlinkId付き） - 辿り着いた node の本文が要るものは
source.get（externalId）で補う - 由来チェーン（origin → 由来 source / 先行 entity）を組み立てて返す
制約
- read-only。persist しない。エッジの追加 / 削除（
link.add/link.remove）は本 skill では行わない（別経路の HITL write） graph.expandのdepthは max 10。cycle guard と edge dedup は traversal 側で担保される- 本 skill は手順書のみで実処理を持たない
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 · 50 lines · 124 tokens per session scan A fdd6908f0b88
provenance-trace is a skill published in the GitHub repository ozzy-labs/suasor (0 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 948 once invoked, about $0.0006 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
graph-mutation-plan
Cookbook for composing an applygraphmutations plan — stable entitykey patterns, the canonical label/edge vocabulary, evidence/invalidation/confidence discipline, and a worked example. Load this when building a non-trivial mutation plan.
review
Structured PR review for pygraphistry. Input: PR number/branch (default current branch PR). Output: findings and convergence artifacts under plans/ /. Method: multi-wave, evidence-first review across spec, correctness, tests, security, code quality, DRY, concurrency, performance, architecture, operability, and…
test-amplification
Methodical bug-driven test amplification for pygraphistry features. Use when hardening a feature area via user-workflow exploration, 5-Whys retrospectives, bug-taxonomy derivation, concrete test planning, implementation, and safety-gated validation.
plan
OPT-IN file-based planning for multi-session tasks. Only use when user explicitly requests it or work spans multiple sessions. For single-session work, prefer your platform's native planning features.
deck-graphify-dark
A dark slide-deck template for AI tools, developer tools, and knowledge graphs, using gradients, floating blurred shapes, graph diagrams, code styling, and glass-like cards.
blueprint-graphs
Add, connect, and configure nodes in Blueprint event graphs and function graphs — function-call/event/branch/timer/custom-event/delegate nodes, Standard Macro nodes (ForEachLoop/ForLoop/WhileLoop/DoOnce/Gate/IsValid/FlipFlop via addmacroinstancenode), macro-graph creation, pin wiring, node layout, arrays, comment…