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/nxtg-ai/forge-plugin/compliancegit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.01296 |
| Opus 5 | $0.00000 | $0.00648 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
compliance 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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/forge:compliance
Scan your dependency tree for license compatibility, generate a Software Bill of Materials (SBOM), and produce a compliance score with conflict resolution guidance.
| Level | L1 Vibe Coder |
| Category | Quality & Testing |
| Syntax | /forge:compliance [--sbom] [--json] [--conflicts-only] [--fix] |
What It Does
/forge:compliance audits every dependency in your project against your project's license (typically MIT). It scans the full dependency tree via npm ls, reads each package's license field, and classifies every dependency as Compatible (MIT, ISC, BSD, Apache-2.0), Conditional (LGPL, MPL), Incompatible (GPL, AGPL, SSPL), or Unknown (missing or custom license). The result is a compliance score from 0-100 with deductions based on severity: incompatible production dependencies cost 10 points each, incompatible dev dependencies cost 5, conditional licenses cost 2, and unknown licenses cost 3.
Beyond license scanning, the command inventories your full tech stack (runtime version, frameworks, language, dependency counts) and can generate a CycloneDX 1.5 SBOM with purl identifiers for every component. The SBOM is saved to .claude/reports/ and is suitable for compliance reporting and supply chain security requirements.
Without this command, license compliance requires manually checking each dependency's license, understanding compatibility rules, and maintaining a spreadsheet. /forge:compliance automates the entire audit and provides actionable resolution guidance for every conflict.
Syntax & Options
/forge:compliance [--sbom] [--json] [--conflicts-only] [--fix]
| Option | Description |
|---|---|
--sbom |
Generate a CycloneDX 1.5 SBOM JSON file and save to .claude/reports/sbom-{date}.json |
--json |
Output all data as raw JSON instead of the formatted report |
--conflicts-only |
Show only license conflicts, skipping the full report |
--fix |
Suggest MIT-licensed alternative packages for each incompatible dependency |
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.
- 2d ago First seen · 130 lines · 0 tokens per session scan A 36585019e137
compliance is a command published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,296 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
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.
privacy-plan
Privacy / GDPR / APPI / store-label audit — plan only, no policy or SDK edits until approved.