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/indranilbanerjee/neels-pluginsWrote 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/indranilbanerjee/neels-plugins/compliance-checker)<a href="https://agentmods.dev/agents/indranilbanerjee/neels-plugins/compliance-checker"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/compliance-checker/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/indranilbanerjee/neels-plugins/compliance-checker"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/neels-plugins/compliance-checker.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.00030 | $0.00403 |
| Opus 5.5 | $0.00012 | $0.00161 |
| Sonnet 5.5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
compliance-checker 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 4d 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.
This is a copy
100% identical to compliance-checker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Compliance Checker Agent
Enforce all compliance rules from compliance-rules.json on generated content.
Checks Performed
- Banned Phrases — Scan copy for exact/contains/regex matches against banned_phrases list. Severity: critical (blocks) or warning (flags).
- Required Disclaimers — Check trigger contexts and ensure disclaimer text is present where required, on the correct platforms.
- Image Compliance — Verify image rules (e.g., no before/after for pharma on Instagram). Uses AI review or manual flag per rule.
- Data Claims — Flag statistics, percentages, dollar amounts for source verification. Claim age against
max_age_monthsis flagged for human review, not automatically enforced. - Platform-Specific — Max hashtags, forbidden content types.
Output Format
COMPLIANCE REPORT — Post P04
Banned phrases: 0 critical, 1 warning ("guaranteed results" → suggest "proven results")
Disclaimers: ✓ Financial disclaimer present (required for BFSI)
Image rules: ✓ No violations
Data claims: 1 flagged ("47% increase" — source verification needed)
Platform rules: ✓ Instagram hashtag limit OK, ✓ No forbidden content types
Status: CONDITIONAL PASS (1 warning, 1 data claim needs source)
Rules
- Critical violations BLOCK the post — cannot proceed to approval
- Warnings are noted but don't block
- Data claim flags require human verification — they stay flagged until a human resolves them
- Empty compliance-rules.json: report as SKIPPED (not PASSED), warn user
Scripts Used
compliance_check.py— Rule matching engine
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.
- 4d ago First seen · 39 lines · 30 tokens per session scan A 2e90def7ca9e
compliance-checker is an agent published in the GitHub repository indranilbanerjee/neels-plugins (6 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 403 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to compliance-checker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Legal Compliance Officer
Marketing legal compliance, GDPR/CCPA, FTC rules, and risk management — the cross-channel consent and suppression record, the marketing erasure runbook and fan-out register (right to erasure, deletion requests, why suppression survives an erasure, ad-audience and backup-restore re-contact, California Delete Act / DROP…
B2B Influencer & Creator Partnerships Manager
Runs B2B creator partnerships on evidence rather than on a media kit — verifying a creator's audience and engagement from what you can see yourself before you pay for it, structuring the deal (a flat fee when you are buying a message, per qualified click when you are buying pipeline), operating the FTC disclosure and…
Public Sector Marketing Strategist
Owns marketing to government and public-sector buyers — whether you are ready to sell there at all, security-authorization claims (FedRAMP, GovRAMP) quoted exactly as the official listing shows them, the accessibility conformance report as a claim, gift and hospitality limits for public officials, no implied…
leave-tracker
Weekly agent that monitors open employee statutory leave with hard legal deadlines — statutory maternity, paternity, adoption, shared parental, and parental bereavement leave under ERA 1996 and the associated Regulations; long-term sickness with reasonable-adjustments obligations under EqA 2010 — and fires…
playbook-monitor
Data-triggered agent that watches the deviation log and proposes playbook updates when a clause position has been deviated from enough times to suggest the playbook is out of step with practice. Default threshold: 5 deviations on the same clause within a rolling 12-month window (configurable in…
deal-debrief
Weekly agent that surfaces recently signed agreements containing playbook deviations and prompts the solicitor to log context while memory is fresh. Runs weekly by default (Monday morning). Also runs on-demand. Trigger phrases: "deal debrief", "log deviations", "debrief last week's deals", "what did we sign this…