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 AiAi-Mastermind/aiai-mastermind-tools-and-skills --skill compliance-checkgit clone --depth 1 https://github.com/AiAi-Mastermind/aiai-mastermind-tools-and-skillsWrote 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/aiai-mastermind/aiai-mastermind-tools-and-skills/compliance-check)<a href="https://agentmods.dev/skills/aiai-mastermind/aiai-mastermind-tools-and-skills/compliance-check"><img src="https://agentmods.dev/badge/skills/aiai-mastermind/aiai-mastermind-tools-and-skills/compliance-check/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/aiai-mastermind/aiai-mastermind-tools-and-skills/compliance-check"><img src="https://agentmods.dev/badge/skills/aiai-mastermind/aiai-mastermind-tools-and-skills/compliance-check.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.00074 | $0.00787 |
| Opus 5 | $0.00037 | $0.00394 |
| Sonnet 5 | $0.00015 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
compliance-check 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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Check
This is the gate. Every draft (caption, text on image, and visual concept) passes through here before it goes anywhere near Mai Marketing Machine. A post that embarrasses the owner with their carrier or their state regulator costs more than a month of content earns. When in doubt, fail it and ask.
Step 1: Load the law
Read brain/compliance/compliance-knowledge-base.md in full. That file is the only source of rules. Do not invent rules that are not written there, and do not waive rules that are. If the draft raises a question the file does not answer, stop and ask the owner, then write the answer into the knowledge base before ruling.
Step 2: Scan the complete draft
Check all three surfaces:
- The caption, line by line
- The text on the image (hooks on visuals are the most-seen words in the post)
- The visual concept itself (what the image implies: fear-mongering, a competitor's branding, a person who is not the owner)
Step 3: Test against every rule category
Walk the knowledge base top to bottom. At minimum:
- Absolute claims about a stranger's coverage or price ("you are overpaying" must read "you might be overpaying")
- Poaching language ("switch to us" must read like "give us a call and we will help you review")
- Guarantees, superlatives, "always," "never," "best," "cheapest"
- Pricing, premiums, percentages, or savings amounts
- Competitor or carrier named negatively, or implied identifiably
- Carrier-specific rules (section 2), state and licensing rules (section 3), agency red lines (section 4)
- Banned phrases log (section 6): exact and near matches
- Stories: real, names removed. Any personal story must trace to brain/voice/story-bank.md. If that file does not exist, no personal story should appear; an invented anecdote is a FAIL
- Client language used where the brain calls for it
Step 4: Rule and report
Produce a verdict in this format and record it in the draft's post.md under Compliance record:
VERDICT: PASS | FAIL
Checked: caption, image text, visual concept
Rules applied: [sections of the knowledge base that were relevant]
If FAIL, for each finding:
- Location: [the exact sentence or image text]
- Concern: [the specific rule it breaks, quoted from the knowledge base]
- Suggested rewrite: [compliant alternative that keeps the hook strength]
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.
- 12d ago First seen · 59 lines · 74 tokens per session scan A 5187060f4873
compliance-check is a skill published in the GitHub repository AiAi-Mastermind/aiai-mastermind-tools-and-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 787 once invoked, about $0.0004 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 skills, from other repositories
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
obsidian-markdown
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.