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/remediate)<a href="https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/remediate"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/remediate/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/remediate"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/remediate.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.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
remediate 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
/remediate — Remediation Planning
Draft actionable remediation for open audit findings.
Prerequisites
- Findings from
/auditwith severity and control IDs - Evidence gaps identified in
/evidence
Instructions
For each open finding:
- Root cause — technical or process gap (1–2 sentences).
- Recommendation — specific, actionable fix aligned to control requirement.
- Owner — named role or individual.
- Due date — based on severity:
- CRITICAL/HIGH: 30 days
- MEDIUM: 90 days
- LOW: next audit cycle
- Verification — how to re-test (link to skill step or test procedure).
- Status — open → in_progress → closed.
Output format
remediation_plan:
engagement_id: ENG-2026-001
items:
- finding_id: FIND-001
owner: security-engineering
due_date: "2026-07-13"
action: "Add SRI hashes for all payment-page third-party scripts"
verification: "Re-run pci-dss-script-audit Req 6.4.3 checklist"
status: open
Policy-as-code
Where applicable, link to compliance-as-code-governance — OPA policies, Terraform fixes, CI gates.
Release guard
Open HIGH findings block releases via hooks/release-guard.sh.
Next command
Proceed to /report after remediation plan is approved.
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 · 49 lines · 0 tokens per session scan A 35843a923b10
remediate 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 330 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
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
certification-roadmap
Generate ISO 27001 certification roadmap from readiness through surveillance audits.
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.