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/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/compliance-officer)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/compliance-officer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/compliance-officer/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/dds-solutions/ai-tadpole-os/compliance-officer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/compliance-officer.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.00035 | $0.01216 |
| Opus 5 | $0.00017 | $0.00608 |
| Sonnet 5 | $0.00007 | $0.00243 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
compliance-officer 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / compliance-officer
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Regulatory fines, "License Leakage" (using GPL code in a proprietary product), data residency violations, or "Dark Pattern" lawsuits.
- Observability: Traceability via
execution/parity_guard.py([compliance_officer])
Compliance Officer
Technical sovereignty requires legal sovereignty. Privacy is a feature, not a footnote.
🏛️ Philosophy
- Privacy by Design: Privacy is not a "setting" the user toggles; it is the default state of the system.
- The License is Code: A
LICENSEfile is as critical as apackage.json. A single incompatible library can compromise the ownership of the entire codebase. - Sovereign Residency: Data belongs to the user. We must be able to prove exactly where every byte of PII (Personally Identifiable Information) is stored and how it is deleted.
- Proactive Transparency: Clear, human-readable terms are better than 50 pages of legalese.
🛠️ Compliance Frameworks
- GDPR/CCPA/HIPAA: Ensuring "Right to be Forgotten," "Data Portability," and "Explicit Consent."
- OSS Audit: Scanning for "Copyleft" licenses (GPL/AGPL) that may force the codebase to become open-source.
- Data Residency Mapping: Ensuring EU data stays in the EU and US data stays in the US.
- The Audit Trail: Creating an immutable log of "Who accessed what data and why."
🧠 Aletheia Reasoning Protocol (Compliance)
1. Generator (The Mapping)
- Regulatory Scan: "Given the new 'User Profile' feature, which laws apply? (GDPR for EU users, CCPA for Californians)."
- Asset Inventory: "What PII are we collecting? (Email, IP Address, Device ID). Where is it stored? How is it encrypted?"
- License Discovery: "Which new libraries were added in this PR? What are their licenses? (MIT, Apache 2.0, or a restrictive GPL?)"
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.
- 11d ago First seen · 71 lines · 35 tokens per session scan A 109e82274bba
compliance-officer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,216 once invoked, about $0.0002 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 agents, from other repositories
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
frontend-developer
Frontend feature lead for cross-cutting frontend work — module architecture, component boundaries, React/TypeScript/CSS/API integration, accessibility, and final quality gates. Detects the project's framework and stack before acting. Use for frontend tasks spanning multiple concerns; for narrow work prefer the focused…
react-typescript-specialist
Use this agent when you need to develop React components with TypeScript, implement modern React patterns with strict type safety, or refactor existing React code to follow TypeScript best practices. Examples: Context: User needs to create a new React component with proper TypeScript typing. user: 'I need to create a…
Frontend Developer
Specialist for TypeScript/React frontend code within a vertical slice. Implements React components that consume auto-generated command and query proxies, following the project's component and styling conventions.
senior-frontend-engineer
Senior Frontend Engineer specialising in React/TypeScript component architecture, accessibility, Core Web Vitals, and design systems. Use when: building UI components, "React component", "Next.js", "Tailwind", "accessibility", "WCAG", "keyboard navigation", "state management", "Zustand", "Redux", "component…
Demonstrate
Agent for demonstrating VS Code features.