Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/dzhokhov/markdown-agent-vault-runpx agentmods add skills/dzhokhov/markdown-agent-vault-ru/case-forensicsWrote 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/dzhokhov/markdown-agent-vault-ru/case-forensics)<a href="https://agentmods.dev/skills/dzhokhov/markdown-agent-vault-ru/case-forensics"><img src="https://agentmods.dev/badge/skills/dzhokhov/markdown-agent-vault-ru/case-forensics.svg" alt="Measured on agentmods" 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.00088 | $0.00704 |
| Opus 5 | $0.00044 | $0.00352 |
| Sonnet 5 | $0.00018 | $0.00141 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
case-forensics 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Case Forensics
Навигация: Индекс скиллов
Overview
Преобразуй неструктурированное обсуждение в воспроизводимый кейс уровня инструкции.
Скилл отвечает за фазу thread -> evidence map -> method extraction -> reproducibility report.
Workflow
1) Parse Timeline
Восстанови хронологию:
- кто действовал,
- какие решения принимались,
- какие изменения вносились,
- что было результатом.
2) Build Evidence Map
Каждый тезис маркируй:
EVIDENCE— подтверждён сообщением/артефактомASSUMPTION— вывод без прямого доказательстваGAP— критично не хватает данных
3) Extract Method
Собери метод в последовательные шаги:
- входные условия
- действия
- инструменты/промты
- контроль качества
- критерий завершения
4) Quantify Outcome
Зафиксируй:
- метрики
before/after - тип эффекта (время/деньги/качество/риск)
- что не сработало
5) Reproducibility Score
Оцени воспроизводимость по контракту из case-data-contract:
input_completenessmethod_specificityartifact_availabilitymetric_verifiability
6) Prepare Final Case
Выдай:
- структурированный кейс
- инструкцию «как повторить за 120 минут»
- блок
GAP+ вопросы для доуточнения из gap-interview-questions
Output
Возвращай разделы:
- Контекст и цель
- Исходные условия
- Метод (шаги)
- Материалы/промты/инструменты
- Результат и метрики
- Что не сработало
- Репликация за 120 минут
- Границы переносимости
- GAP и вопросы
Quality Gates
- Нет шагов без входа/выхода.
- Любая числовая метрика имеет источник в треде.
- Любая гипотеза без подтверждения помечена как
ASSUMPTION. - Есть явные ограничения применимости кейса.
Anti-Patterns
- Не выдавать «историю успеха» как методологию.
- Не скрывать провалы/ограничения.
- Не подменять
GAPдогадками.
References
What ships with it
6 files 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.
- 8d ago First seen · 100 lines · 88 tokens per session scan A f458ac81143b
case-forensics is a skill published in the GitHub repository dzhokhov/markdown-agent-vault-ru (2 stars, last pushed yesterday), licensed MIT. It adds 88 tokens to every session and 704 once invoked, about $0.0004 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
pos-verify
Use this immediately after files are created, edited, moved, deleted, or materially rewritten inside PersonalOS. Verifies that new truth was routed to the correct owner, written in the correct file shape, and still follows POS conventions. Do NOT use for whole-vault deep audits; use system-health-check.
skillify
Use this when {{username}} asks to skillify a repeated workflow, determine whether it deserves a reusable PersonalOS skill, or harden an existing workflow into a tested resolver-reachable capability. Do NOT use for one-off notes, ordinary execution, or already-specified skill authoring; use write-skill.
write-skill
Use this when the user wants to create a new shared PersonalOS skill under skills/ or revise a specified PersonalOS skill and the scope is already clear. Do NOT use for raw workflow capture or deciding whether work should become a skill; use skillify first. Do NOT use for repo-local or agent-local skills unless…
priority-dashboard
Use this to rebuild, inspect, or temporarily steer {{username}}'s current PersonalOS priority dashboard from canonical Actions, Attention Triggers, and owner context. Do NOT use it to create, complete, or independently manage tasks; use task-manager for Action and Trigger lifecycle changes.
lint-brain
Run health checks over the brain vault - find orphan notes, broken wikilinks, missing frontmatter, stale projects, and missing cross-links. Use when asked to "lint the brain", "health check", "vault hygiene", or "/lint-brain".
ingest-article
Ingest an article from a URL or raw text into the brain vault. Extracts key knowledge, determines placement, creates or updates notes, and links to relevant projects. Use when the user shares a URL or text and wants to absorb it into their knowledge base.