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/scope)<a href="https://agentmods.dev/commands/vaquarkhan/compliance-agent-skills/scope"><img src="https://agentmods.dev/badge/commands/vaquarkhan/compliance-agent-skills/scope.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.00000 | $0.00291 |
| Opus 5 | $0.00000 | $0.00146 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
scope 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.
What it actually says
/scope — Engagement Scoping
Define the audit boundary before any control testing.
Instructions
- Identify frameworks — HIPAA, PCI-DSS v4.0, SOC 2 (list all that apply).
- List in-scope systems — URLs, apps, databases, MCP servers, identity providers, cloud accounts.
- Classify data — ePHI, CHD/SAD, confidential, public.
- Document exclusions with rationale.
- Record authorization — written approval to scan/test production (if applicable).
- Assign engagement ID —
ENG-{YYYYMMDD}-{slug}.
Output artifact
Create scope-{engagement-id}.json:
{
"engagement_id": "ENG-2026-001",
"created_at": "2026-06-13T00:00:00Z",
"frameworks": ["HIPAA-Security-Rule"],
"in_scope": [],
"out_of_scope": [],
"data_classes": [],
"approver": "",
"authorization_date": null
}
Apply preset
If industry/cloud named, read matching presets/*/PRESET.md.
Skill
Load using-compliance-agent-skills Step 2 (Scope definition).
Next command
Proceed to /audit when scope 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.
- 8d ago First seen · 42 lines · 0 tokens per session scan A d472cb317bfd
scope is a command published in the GitHub repository vaquarkhan/compliance-agent-skills (2 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 291 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
service-auditor-prep
Generate complete auditor-ready evidence package for SOC 2.
soa-generator
Generate ISO 27001 Statement of Applicability (SOA) with control selection justifications.
continuous-monitoring-setup
Set up NIST 800-53 continuous monitoring per RA-5, SI-4, and CA-7.
control-tailor
Interactive NIST 800-53 control tailoring for specific baselines and environments.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
ssp-section-generate
Generate System Security Plan (SSP) sections for NIST 800-53 controls.