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 skills add ShulkwiSEC/bb-huge --skill compliancegit clone --depth 1 https://github.com/ShulkwiSEC/bb-hugeWrote 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/shulkwisec/bb-huge/compliance)<a href="https://agentmods.dev/skills/shulkwisec/bb-huge/compliance"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/compliance/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/skills/shulkwisec/bb-huge/compliance"><img src="https://agentmods.dev/badge/skills/shulkwisec/bb-huge/compliance.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.00090 | $0.04343 |
| Opus 5 | $0.00045 | $0.02171 |
| Sonnet 5 | $0.00018 | $0.00869 |
| Haiku 4.5 | $0.00009 | $0.00434 |
Grade A, and why
compliance scanned grade A with 1 finding 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 6d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Search for eval(), exec(), subprocess/child_process with user input How it starts
The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASVS 5.0 Compliance Assessment
You are a senior application security engineer performing a formal ASVS 5.0 compliance assessment. Your job is to evaluate a codebase (and optionally architecture diagrams) against every applicable OWASP ASVS 5.0 control and produce an evidence-backed compliance matrix.
Do not guess. Read actual files before assigning a verdict to any control.
Request: $ARGUMENTS
Arguments
Parse from the user's invocation:
CODEBASE_PATH— absolute path to the codebase to assess (required)diagrams— comma-separated list of paths to architecture diagram files (optional; PNG/JPG/SVG/Mermaid .md/.mmd/draw.io .xml)depth—quick|standard|thorough(default:standard)
If CODEBASE_PATH is missing, ask the user before proceeding.
Control Data
All 346 ASVS 5.0 controls live in the companion CSV at skills/compliance/refs/asvs-5.0.csv.
Read this file first. It has 7 columns:
| Column | Meaning |
|---|---|
chapter_id |
e.g. V1 |
chapter_name |
e.g. Encoding and Sanitization |
section_id |
e.g. V1.2 |
section_name |
e.g. Injection Prevention |
req_id |
e.g. V1.2.4 — the control ID used throughout the output |
req_description |
Full OWASP requirement text |
L |
Level: 1 (baseline), 2 (standard), 3 (advanced) |
Group controls by chapter_id before starting assessment.
Depth Presets
| Depth | Chapters assessed | Evidence depth |
|---|---|---|
quick |
V1, V6, V8, V11, V13 (highest-risk five) | One evidence source per control |
standard |
All 16 chapters | One to two evidence sources per control |
thorough |
All 16 chapters | Multiple evidence sources per control; cross-reference architecture diagrams for all applicable controls |
For chapters not assessed at the chosen depth, set every control in that chapter to NOT_ASSESSED in the output.
Phase 1 — Load Controls and Detect Stack
1a — Load the ASVS CSV
Read skills/compliance/refs/asvs-5.0.csv. Parse all rows. Group by chapter_id. You now have the full list of controls to assess.
What ships with it
3 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.
- 6d ago First seen · 418 lines · 90 tokens per session scan A 87f81d8ee8bc
compliance is a skill published in the GitHub repository ShulkwiSEC/bb-huge (22 stars, last pushed 2mo ago), licensed MIT. It adds 90 tokens to every session and 4,343 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
gdpr-gate
This skill should be used when auditing diffs or plans for GDPR/CCPA/HIPAA compliance gaps.
legal-generate
This skill should be used when generating draft legal documents for a project or company. It gathers company context interactively, invokes the legal-document-generator agent, and writes markdown output.
legal-audit
This skill should be used when auditing existing legal documents for compliance gaps, outdated clauses, missing disclosures, and cross-document consistency. It scans a project for legal documents and displays findings inline.
clo
Orchestrates the legal domain -- assesses legal document posture, recommends actions, and delegates to legal specialist agents. Use individual legal agents for focused tasks; use this agent for cross-cutting legal strategy and multi-agent coordination.
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
gesellschaftsrechtliche-satzungen-agb
Für Gesellschaftsrechtliche Satzungen AGB Abgrenzung: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: gesellschaftsrechtliche-satzungen-agb.