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.
git clone --depth 1 https://github.com/vaquarkhan/compliance-agent-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/commands/vaquarkhan/compliance-agent-skills/evidence)<a href="https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/evidence"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/evidence/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/commands/vaquarkhan/compliance-agent-skills/evidence"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/evidence.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.00000 | $0.00266 |
| Opus 5 | $0.00000 | $0.00133 |
| Sonnet 5 | $0.00000 | $0.00053 |
| Haiku 4.5 | $0.00000 | $0.00027 |
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 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.
What it actually says
/evidence — Evidence Collection
Collect, hash, and package audit artifacts for assessors.
Prerequisites
- Completed
/auditwith documented findings - Skill:
soc2-evidence-collection(cross-framework evidence mechanics)
Instructions
- Inventory required evidence per control/finding from audit worksheet.
- Collect artifacts — exports, screenshots, log samples, config snapshots.
- Compute SHA-256 for each file.
- Populate manifest —
templates/audit-evidence-manifest.yaml. - Chain of custody — record collector, timestamp, source system.
- Store bundle in
evidence-bundle/{engagement-id}/(gitignored locally).
Integrity
sha256sum evidence/* > evidence-bundle/sha256sums.txt
Update bundle_hash in manifest after all artifacts listed.
Rules
- No raw PHI/PAN in evidence filenames or unencrypted shares
- Redact screenshots before external transfer
- Prefer read-only MCP queries for database evidence
Output
Completed audit-evidence-manifest.yaml ready for auditor handoff.
Next command
Proceed to /remediate for open findings, or /report if clean.
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 · 40 lines · 0 tokens per session scan A 93b0160b9794
evidence is a command published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 266 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
soa-generator
Generate ISO 27001 Statement of Applicability (SOA) with control selection justifications.
ssp-section-generate
Generate System Security Plan (SSP) sections for NIST 800-53 controls.
generate-tsc-matrix
Generate Trust Service Criteria implementation matrix.
service-auditor-prep
Generate complete auditor-ready evidence package for SOC 2.
testing-plan
Digital operational resilience testing requirements and planning under DORA.
continuous-monitoring-setup
Set up NIST 800-53 continuous monitoring per RA-5, SI-4, and CA-7.