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 agentmods add commands/hermeticormus/libresecops-claude-code/evidence-chaingit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/commands/hermeticormus/libresecops-claude-code/evidence-chain)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/evidence-chain"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/evidence-chain.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 | $0.00000 | $0.01192 |
| Opus 5 | $0.00000 | $0.00596 |
| Sonnet 5 | $0.00000 | $0.00238 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
evidence-chain 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 5d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evidence-chain
Document a chain of custody record for collected digital evidence, ensuring integrity and admissibility.
Trigger
Use every time digital evidence is:
- Collected from a system
- Transferred between locations or storage
- Accessed for analysis
- Copied or imaged
- Returned or disposed of
Chain of custody documentation must begin at the moment evidence is identified and continue through final disposition. Gaps in the chain compromise evidence integrity.
Input
- Required: Evidence description (what is it, where does it come from)
- Required: Action being performed (collection, transfer, analysis, storage, disposal)
- Required: Person performing the action
- Optional: Case ID (should be established by /forensic-plan)
- Optional flag:
--verify-- include hash verification step - Optional flag:
--legal-- use formal legal chain of custody format
Process
-
Evidence Identification: Document what the evidence is:
- Physical description (device type, serial number, model, capacity)
- Digital description (disk image, memory dump, log export, network capture)
- Source system (hostname, IP, location)
- Relevance (why this evidence matters to the investigation)
-
Integrity Verification: Compute and record cryptographic hashes:
- SHA-256 hash of the evidence file or disk
- Hash recorded at time of collection
- Hash verified at every subsequent access
- Any hash mismatch is a critical event that must be documented and investigated
-
Chain of Custody Entry: Record the custody transfer:
- Date and time (UTC)
- Person releasing custody (name, role, contact)
- Person receiving custody (name, role, contact)
- Purpose of transfer (collection, analysis, storage, legal hold)
- Storage location (locked cabinet, evidence locker, encrypted storage, forensic workstation)
- Any changes to evidence packaging or storage conditions
-
Storage Requirements: Document storage conditions:
- Physical security (locked room, access log)
- Environmental protection (temperature, humidity for hardware)
- Digital security (encryption at rest, access controls)
- Retention period (legal hold duration, retention policy)
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.
- 5d ago First seen · 122 lines · 0 tokens per session scan A 83bd835ee32c
evidence-chain is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,192 tokens. 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 commands, from other repositories
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
sicario.controls
Generate or update docs/compliance/control-applicability.md.
sicario.evidence
Generate evidence artifacts.
compliance-check
Check IaC files against a specific compliance framework.
ios-privacy
Prepare privacy labels, permissions, policy links, and data-use truth for iOS release.
checklist
Generate a custom checklist for the current feature based on user requirements.