Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSnpx agentmods add skills/dds-solutions/ai-tadpole-os/adg-governanceWrote 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/dds-solutions/ai-tadpole-os/adg-governance)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/adg-governance"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/adg-governance/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/dds-solutions/ai-tadpole-os/adg-governance"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/adg-governance.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.00034 | $0.00903 |
| Opus 5.5 | $0.00014 | $0.00361 |
| Sonnet 5.5 | $0.00007 | $0.00181 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
adg-governance 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 9d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / adg-governance
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy v1 claims, unverified documentation divergence.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Active Documentation Guard (ADG v2) Protocol
Purpose: Guarantee zero architectural drift between codebase reality and sovereign documentation through automated AST symbol mapping and machine-maintained manifests. Workflow Binding: Used during
/audit,/refactor, and pre-commit verification.
🎯 Progressive Disclosure & L3 Reference Index
Read REQUIRED core standards below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide / Tool | Purpose | Trigger / When to Load |
|---|---|---|
references/adg_v2_manifest_and_blast_rules.md |
Header specifications, forbidden v1 anti-patterns, AST blast radius tooling | Writing or updating code file headers |
scripts/adg_linter.py |
Deterministic scanner for forbidden v1 claims (Witness Tests:) and @docs tags |
Pre-commit file header validation |
🏛️ Core Architectural Invariants
- No Hand-Written Fact Claims: Never write
Witness Tests:or freeformInvariants:in source file headers. Those are forbidden v1 anti-patterns flagged bynpm run adg:lint. - Machine-Maintained Manifest: Test witness relationships are automatically derived by
npm run adg:generateintoadg.manifest.json. - Mandatory Header Block: All production source files must contain the standard
@docs ARCHITECTURE:...block. - Mandatory Pre-Refactor Guard: Before modifying shared contracts, run
npm run graph:blast:guard -- --path <file>to map affected callers and callees.
🛡️ Socratic Gate: Blast Radius & Documentation Invariants
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 79 lines · 34 tokens per session scan A 16feb752f551
adg-governance is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 903 once invoked, about $0.0001 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-10-18.
Other skills, from other repositories
isolating-product-facade-contracts
Plan and execute product isolation migrations to a facade plus contract layer in PostHog, following the Visual review architecture. Use when a product still exposes internals (models/logic/views) across boundaries and needs migration toward contracts.py + facade/api.py + presentation separation, with a PR strategy…
walkeros-understanding-development
Use when contributing to walkerOS, before writing code, or when unsure about project conventions. Covers build/test/lint workflow, XP principles, folder structure, and package usage.
qa-frontend
Internal PostHog developer frontend/browser QA skill. Use only when a PostHog developer explicitly asks to run frontend QA, browser-test a PR, verify a UI flow against the local PostHog stack, use qa-frontend, or QA current frontend changes with browser/runtime evidence, or to make a feature reel (see reel mode…
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…
splitting-oversized-modules
Split an oversized Python module (a thousand-plus-line logic.py, models.py, api.py, or its test file) into a package of one module per concern, mechanically and provably without changing behavior. Use on a request to split / break up / decompose a god module or move functions out of one, once a human has agreed to…
establishing-code-ownership
Determine which PostHog team owns a file, directory, or code path, or enumerate all code a team owns (via distributed owners.yaml, products//product.yaml, and .github/CODEOWNERS). Use when assigning a reviewer, attributing a bug or slow query to a team, routing work, scoping a team-wide audit, or answering "who owns…