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/ololand-ai/ololand-plugins/regulator-exportgit clone --depth 1 https://github.com/ololand-ai/ololand-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/commands/ololand-ai/ololand-plugins/regulator-export)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/regulator-export"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/regulator-export.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 | $0.00050 | $0.00768 |
| Opus 5 | $0.00025 | $0.00384 |
| Sonnet 5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
regulator-export 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 3d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/regulator-export
You are queueing a compliance-framework export. The Celery task tasks.regulator_export_tasks.generate_regulator_export builds a tarball with:
- Every
agent_runsrow in the window (id, snapshots, grader verdicts, cost, status). - All
agent_spansfor those runs (tool calls, model calls, compactions). - All
output_artifactsproduced (CIMs, IC memos, forensic PDFs). - Control-map metadata for the named compliance framework so each artifact is keyed to the relevant control.
This command requires admin or compliance role.
Required inputs
- framework — compliance framework id. The tool validates against
available_frameworks()and returns the list on a bad input. Ask the user if unclear. - from_date — ISO
YYYY-MM-DD, inclusive. - to_date — ISO
YYYY-MM-DD, inclusive.
Optional:
- deal_ids — list of specific deals to restrict the export to. Omit for company-wide.
Action
-
Call
mcp__ololand__request_regulator_exportwith the collected fields. -
On success, the response is a
RegulatorExportrow instatus: "queued". Surface:Regulator export queued Export id: <id> Framework: <framework> Window: <from_date> to <to_date> Deals: <all|specific list> Status: queuedTell the user to poll
mcp__ololand__get_regulator_export <export_id>for completion. Typical latency: minutes to hours depending on window size and corpus. -
When polling shows
status: "completed", surfacetarball_uri,tarball_sha256(for chain-of-custody attestation), andexpires_at. The URI is a signed download link. -
On error from the request, surface the
error_codeand explanation:bad_request(unknown framework) — surface theavailablelist verbatim.insufficient_role— user is not admin/compliance.no_company— agent key is not company-scoped.
When to use
- A regulator (SEC, FINRA, FCA, etc.) requests a defensible audit trail.
- Internal compliance review (SOC 2 controls, ISO 27001, EU AI Act conformity).
- IC-mandated reproducibility exercise for a closed deal.
- Periodic compliance archive (monthly / quarterly).
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.
- 3d ago First seen · 64 lines · 50 tokens per session scan A a04c4464d784
regulator-export is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 50 tokens to every session and 768 once invoked, about $0.0003 per session on Opus 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 commands, from other repositories
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.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
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.
compliance-audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.