evidence

A research workflow for selecting passages from primary source files and testing how well they support sections of a study. It records exact quotes with their file locations and evaluates their usefulness.

In plain words
What is it for?
Use it to find evidence in a raw_primary folder, score candidate passages, choose main and supporting quotes, test their connection to a thesis, and update evidence notes.
Why use it?
It helps prevent unsupported claims and invented quotations. It also makes weaknesses in the available evidence visible.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/josefslerka/study-kit/evidence
Clone the repo
git clone --depth 1 https://github.com/josefslerka/study-kit

Made for: Claude Code.

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 277 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.00277
Opus 5 $0.00016 $0.00138
Sonnet 5 $0.00007 $0.00055
Haiku 4.5 $0.00003 $0.00028

Measured 2d ago against content hash 4db1c1a4b2d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evidence 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 2d 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.

cs/.claude/commands/evidence.md · 14 lines

What it actually says

Proveď fázi 2.4 a navazující 3.1 dle CLAUDE.md.

2.4: pro každou sekci PROHLEDEJ raw_primary/ a najdi 4–6 kandidátních pasáží S PROVENANCE (soubor + lokace, citát doslovně). Ohodnoť 1–5 (relevance, přesvědčivost, reprezentativnost, multifunkčnost, nezávislost), vyber hlavní + podpůrné důkazy. RED FLAG: žádná pasáž > 3 → sekce nepodložitelná. NIKDY nedoplňuj vymyšlený citát — nahlas, že korpus oporu nedává.

3.1: pro každý klíčový citát proveď 5 testů (parafráze, spojení s tezí, vrstevnatost ≥2 z 5, přechod, vzorový odstavec). Zapiš/dopiš process/evidence.md, zaloguj, navrhni /prechody.

Changes

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.

  1. 2d ago First seen · 14 lines · 33 tokens per session scan A 4db1c1a4b2d7

Subscribe to this mod's changes

evidence is a command published in the GitHub repository josefslerka/study-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 277 once invoked, about $0.0002 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.