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 JetXu-LLM/DocMason --skill provenance-tracegit clone --depth 1 https://github.com/JetXu-LLM/DocMasonWrote 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/jetxu-llm/docmason/provenance-trace)<a href="https://agentmods.dev/skills/jetxu-llm/docmason/provenance-trace"><img src="https://agentmods.dev/badge/skills/jetxu-llm/docmason/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/jetxu-llm/docmason/provenance-trace"><img src="https://agentmods.dev/badge/skills/jetxu-llm/docmason/provenance-trace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00917 |
| Opus 5 | $0.00012 | $0.00458 |
| Sonnet 5 | $0.00005 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
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 10d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provenance Trace
Use this skill when the task is to prove where a knowledge object or answer came from.
Use it directly for explicit provenance or citation requests, or let ask route here automatically.
Direct public trace remains a legal operator provenance surface.
It does not substitute for canonical ask when the user is really asking for ordinary answer completion.
Required Capabilities
- local file access
- shell or command execution
- ability to inspect structured JSON output
If the agent cannot inspect the local trace artifacts or source evidence, stop and explain that reliable provenance tracing is not possible.
Procedure
- Use
currentas the default knowledge-base target unless the task explicitly says otherwise. - For citation-first tracing, run:
docmason trace --source-id <source_id> --json --compact- optionally add
--unit-id <unit_id>for unit-level detail - if you genuinely need nested support objects or detailed render metadata, rerun full
--jsonto a local file and inspect it selectively instead of pasting the raw payload into chat - keep DocMason workspace commands sequential inside the same workspace session; do not overlap
trace,retrieve,sync,status, orvalidate-kbwhile a lease-owning command is still active
- For answer-first tracing, run:
docmason trace --answer-file <path> --json --compact- or
docmason trace --session-id <session_id> --json --compact - do not invent a new freeform
--source-refsurface in this phase; public trace remains ID-first
- Inspect:
payload_detail- any inherited
reference_resolutionblock on answer-first traces answer_state- source provenance
- unit consumers
- incoming and outgoing relations
- grounding status for each answer segment
- compact
supporting_source_ids - compact
supporting_unit_ids supporting_artifact_idssupporting_overlay_unit_ids- segment
support_lane_counts - segment
artifact_support_count - segment
semantic_support_count - artifact
focus_render_assetswhen present - render-inspection requirements
- if the provenance judgment depends on nested
artifact_supports,semantic_supports, overlay consumed inputs, covered slots, blocked slots, render refs,render_page_span,bbox,normalized_bbox, or sidecar paths, inspect a file-first full trace capture instead of the raw chat payload
- If any segment is only partially grounded or unresolved, say so explicitly and avoid pretending stronger provenance than the trace supports.
- Return the final provenance or groundedness judgment to the main agent instead of treating trace output as a final user answer by itself.
- If you need to export a scratch trace note and the user did not specify a destination, place it under
runtime/agent-work/.
What ships with it
1 file 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.
- 10d ago First seen · 76 lines · 24 tokens per session scan A 1bd17c611352
provenance-trace is a skill published in the GitHub repository JetXu-LLM/DocMason (135 stars, last pushed 6d ago), licensed Apache-2.0. It adds 24 tokens to every session and 917 once invoked, about $0.0001 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-30.
Other skills, from other repositories
openkb-deck-neon
A skill for creating a single-file HTML slide deck from content stored in OpenKB, a knowledge-base chat system. It defines a dark, high-tech visual style using neon colors, glow effects, and glass-like panels.
openkb-deck-editorial
A tool for creating a single-file HTML slide presentation from compiled knowledge-base content. Its visual style uses a warm cream background, serif typography, and brick-red accents.
openkb-html-critic
Use to review a generated HTML deck or single-page artifact for visual quality and structural correctness. Especially good at catching CSS specificity bugs where slide-modifier classes (.divider, .center, .q, .flow etc.) accidentally override the base .slide{display:none} and cause one slide to stack on top of every…
transformer-attention
Use when reasoning about Transformer self-attention, multi-head attention, positional encoding, masked decoder attention, or why attention replaced recurrence/convolutions in sequence models; not for generic NLP or unrelated attention topics.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.