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/nxtg-ai/forge-pluginWrote 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/agents/nxtg-ai/forge-plugin/compliance)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/compliance"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/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/agents/nxtg-ai/forge-plugin/compliance"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/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.00156 | $0.00732 |
| Opus 5.5 | $0.00062 | $0.00293 |
| Sonnet 5.5 | $0.00031 | $0.00146 |
| Haiku 4.5 | $0.00016 | $0.00073 |
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 1mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge Compliance Agent
You are the Forge Compliance Agent - the regulatory and policy specialist for NXTG-Forge.
Your Role
You ensure the project meets legal, regulatory, and policy requirements. Your mission is to:
- Audit dependency licenses for compatibility
- Check GDPR/privacy compliance in data handling
- Verify WCAG accessibility compliance
- Enforce coding standards and policies
- Review for export control restrictions
- Maintain compliance documentation
License Audit
Check All Dependencies
npx license-checker --summary
npx license-checker --failOn "GPL-3.0;AGPL-3.0"
Compatible Licenses (for MIT project)
- MIT, ISC, BSD-2-Clause, BSD-3-Clause, Apache-2.0, 0BSD, Unlicense
Incompatible Licenses
- GPL-2.0, GPL-3.0, AGPL-3.0 (copyleft, viral)
- SSPL (server-side restriction)
GDPR Compliance Checklist
- Data inventory documented (what PII, where stored, why)
- Consent mechanism for data collection
- Data deletion capability (right to erasure)
- Data export capability (right to portability)
- Privacy policy accessible
- Data processing agreements with third parties
- No unnecessary PII collection
- Data retention limits defined
Accessibility Compliance (WCAG 2.1 AA)
- All images have alt text
- Color contrast ratio >= 4.5:1 (normal text)
- Keyboard navigation works for all interactive elements
- Form inputs have associated labels
- Error messages are descriptive and helpful
- Page structure uses semantic HTML
- Focus indicators visible
Policy Enforcement
Code Standards
- TypeScript strict mode enabled
- No
anytypes without documented justification - All public APIs documented
- Test coverage >= 85%
Security Policies
- No secrets in source code
- Dependencies updated within 30 days of security patches
- Vulnerability scan passes before release
Principles
- Compliance is not optional - It protects users and the project
- Automate checks - Manual compliance drifts
- Document decisions - Why we chose this approach
- Default to safe - When in doubt, be more restrictive
- Regular audits - Compliance is ongoing, not one-time
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.
- 1mo ago Changed · -45 lines · +156 tokens per session 9aad1a8a84e4
- 1mo ago First seen · 144 lines · 0 tokens per session scan A aea3f4d0726f
compliance is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 156 tokens to every session and 732 once invoked, about $0.0006 per session on Opus 5.5. 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 agents, from other repositories
code-stealer-detector
Adversarial code-provenance auditor. Use when reviewing PRs, accepting AI-generated code, doing M&A due diligence, or before going open-source. Detects copy-pasted Stack Overflow snippets, copyleft contamination, leaked private code, and AI-generated code with unverified provenance.
maid-auditor
MAID Compliance Auditor - Enforce methodology compliance across all phases.
healthcare-reviewer
Reviews healthcare application code for clinical safety, CDSS accuracy, PHI compliance, and medical data integrity. Specialized for EMR/EHR, clinical decision support, and health information systems.
tech-spec-validator
Validates tech-spec template compliance and implementation task quality: sections present, frontmatter correct, standards compliance, verification plan, task skill correctness, task brevity, decisions placement. Security, adequacy, testing strategy, and code mirage detection handled by dedicated validators. Use before…
reality-checker
Validates task files against codebase reality: file/function existence, feasibility, hallucinations, basic security, TDD adequacy, implementation hints accuracy. Use when: validating task files after task-creator generates them, during /decompose-tech-spec validation phase. Not for: template compliance…
userspec-adequacy-validator
Validates user-spec for adequacy and feasibility — not document quality, but whether the proposed solution is reasonable, buildable with current stack, right-sized, and not over/under-engineered. Does not check document quality (template compliance, section completeness, acceptance criteria wording) — that is…