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 jh941213/codex-lattice --skill data-governancegit clone --depth 1 https://github.com/jh941213/codex-latticeWrote 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/jh941213/codex-lattice/data-governance)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/data-governance"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/data-governance.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.1 | $0.00042 | $0.00275 |
| Opus 5 | $0.00021 | $0.00138 |
| Sonnet 5 | $0.00008 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
data-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 7d 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.
What it actually says
Data Governance
Use this skill when a change touches PII, privacy, retention, data classification, access control, audit logs, analytics events, schema ownership, or compliance-sensitive data.
Workflow
- Identify data classes: public, internal, confidential, secret, PII, regulated.
- Identify where data enters, persists, leaves, and gets logged.
- Confirm validation and minimization at external boundaries.
- Confirm retention and deletion expectations.
- Check access control and audit trail requirements.
- Check whether migrations preserve ownership and rollback expectations.
- Update
docs/harness/DATA_GOVERNANCE.md,docs/harness/DATA_MODEL.md, anddocs/harness/SECURITY_POLICY.md.
Red Flags
- PII in logs, model-visible files, telemetry, screenshots, or test fixtures.
- Broad admin access without audit.
- Analytics events with raw user content.
- Data retention without deletion path.
- Schema changes without migration verification.
Required Output
Return data classes, flows, storage, retention, access controls, audit evidence, and unresolved compliance risk.
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.
- 7d ago First seen · 31 lines · 42 tokens per session scan A da6440dd51e7
data-governance is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 275 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-30.
Other skills, from other repositories
dsar-fulfillment
Daily GDPR data-subject-access-request runbook. Verifies each incoming request from Gmail, locates the subject's data read-only across every relevant Postgres table, compiles an access-or-deletion report in Google Docs within the {{sladays}}-day SLA, and flags it to {{legalreviewchannel}} for a lawyer to approve.…
state-assets-register
Download nightly XML extracts and the XSD for Estonia's State Real Estate Register (RKVR).
Data Retention Schedule Review
Use when reviewing a draft or existing data retention schedule to inventory data categories against stated purposes, collect retention-period facts, flag legal-hold interactions, and surface orphaned-data and vendor-coverage gaps for attorney review.
lgpd-consent-schema
Design the database schema for a versioned, append-only consent ledger that satisfies LGPD Art. 8 (free, informed, unambiguous consent for a specific purpose) and Art. 9 (information rights). Use when user asks for "consent schema", "consent ledger", "schema de consentimento", "Prisma consentimento", "consent…
opensearch-agent-right-to-be-forgotten
Fulfil GDPR "right to be forgotten" / erasure and CCPA deletion requests against OpenSearch by finding and removing a person's personal data — including INDIRECT contextual identification, where an individual is identifiable without their name, email, or ID ever appearing (e.g. "the solo frontend engineer on duty…
db-temporal-history
Audit temporal and lifecycle modeling — soft-delete consistency and its uniqueness/query traps, presence and integrity of an audit/history trail, and retention / GDPR right-to-erasure handling (hard delete vs anonymization, retention windows). Module M8. Feeds the Design & Integrity score (Temporal category).