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 Kshitijpalsinghtomar/depth-skills --skill ds-provenancegit clone --depth 1 https://github.com/Kshitijpalsinghtomar/depth-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/kshitijpalsinghtomar/depth-skills/ds-provenance)<a href="https://agentmods.dev/skills/kshitijpalsinghtomar/depth-skills/ds-provenance"><img src="https://agentmods.dev/badge/skills/kshitijpalsinghtomar/depth-skills/ds-provenance/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/kshitijpalsinghtomar/depth-skills/ds-provenance"><img src="https://agentmods.dev/badge/skills/kshitijpalsinghtomar/depth-skills/ds-provenance.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.00025 | $0.01628 |
| Opus 5 | $0.00013 | $0.00814 |
| Sonnet 5 | $0.00005 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
provenance 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 12d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PROVENANCE — Evidence Tagger & Confidence Calibrator
You are about to deliver claims. Some you know. Some you inferred. Some you guessed. Your output treats all three identically — same tone, same phrasing, same implicit confidence.
The user cannot tell which is which. A fact and a guess, written in the same authoritative voice, look the same. The user either trusts everything (risky) or questions everything (wasteful). This skill makes the difference visible.
The Failure Mode You Must Recognize
You are about to write:
"PostgreSQL JSONB columns support GIN indexing, which will give you fast queries and your team will find the migration straightforward."
Three claims, three different evidence levels, one uniform confident voice:
- "JSONB supports GIN indexing" — documented fact
- "will give you fast queries" — inference (depends on their specific query patterns)
- "team will find it straightforward" — pure guess (you don't know the team)
This is epistemic flattening: collapsing facts, inferences, and guesses into a single confident tone. The user makes decisions based on the guess as if it were a fact.
The Protocol
Step 1 — EXTRACT AND TAG EVERY CLAIM
Read your answer. Extract every factual claim, recommendation, and prediction. Tag each one:
EVIDENCE LEDGER
────────────────────────────────────────
[F] FACT — Established, well-documented knowledge. Would appear in
official documentation or authoritative references.
Evidence standard: you could cite the source.
[I] INFERENCE — Logically derived from facts, but not directly stated
in any source. Reasonable conclusion with a possible gap.
Evidence standard: the reasoning chain is explicit.
[G] GUESS — Plausible but unverified. Based on pattern matching,
analogy, or partial similarity. No direct evidence.
Evidence standard: none. Pattern-based only.
────────────────────────────────────────
Claim 1: "[exact claim text]"
Tag: [F / I / G]
Basis: [for F: what source. For I: what reasoning chain.
For G: what pattern or analogy]
Risk note: [for I and G: what would make this wrong]
Claim 2: "[exact claim text]"
Tag: [F / I / G]
Basis: [source / reasoning / pattern]
Risk note: [what would make this wrong]
...
────────────────────────────────────────
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.
- 12d ago First seen · 198 lines · 25 tokens per session scan A a9ebf676d537
provenance is a skill published in the GitHub repository Kshitijpalsinghtomar/depth-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,628 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-31.
Other skills, from other repositories
vox-video-director
Turn ONE topic into a finished Vox-style paper-collage explainer / ad video, end to end with Aliyun Bailian CLI + local ffmpeg — script, collage keyframes, motion, voice-over, music, captions, all automated. Use this whenever the user wants a "Vox style" video, a paper/torn-paper collage animation, a "motion collage"…
bailian-train-deploy
A workflow for using Alibaba Cloud’s Bailian command-line tool to fine-tune or directly deploy AI models as callable services. It covers text, speech-synthesis, image-generation, and video-generation models.
api-database-mongodb
Native MongoDB driver (the mongodb npm package) - MongoClient lifecycle, typed collections, CRUD result shapes, cursors, aggregation pipelines, index design, transactions.
ai-infrastructure-ollama
Local LLM inference with the Ollama JavaScript client -- chat, streaming, tool calling, vision, embeddings, structured output, model management, and OpenAI-compatible endpoint.
ai-orchestration-langchain
LangChain.js patterns for building LLM applications — chat models, LCEL chains, prompt templates, structured output, agents, tools, RAG, streaming, and LangSmith tracing.
ai-provider-cohere-sdk
Official Cohere TypeScript SDK patterns -- CohereClientV2, chat, embeddings, rerank, RAG with citations, tool use, streaming, and model selection.