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 jeremylongworth-source/AgentSkills --skill ai-governance-checklistgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/ai-governance-checklist)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/ai-governance-checklist"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/ai-governance-checklist/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/jeremylongworth-source/agentskills/ai-governance-checklist"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/ai-governance-checklist.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.00058 | $0.00350 |
| Opus 5 | $0.00029 | $0.00175 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
ai-governance-checklist 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.
What it actually says
AI Governance Checklist
Core Workflow
- Identify AI use cases, autonomy level, data sensitivity, users, impacted stakeholders, and deployment stage.
- Define governance domains: ownership, data, security, privacy, legal, compliance, human oversight, monitoring, auditability, training, and change management.
- Convert governance needs into checklist items, owners, evidence, and gates.
- Separate pilot governance from production governance.
- Identify policies, reviewers, and controls that must exist before scale.
- State unresolved governance gaps and recommended next review.
Safety Rules
- Do not present governance checklists as legal, compliance, or security approval.
- Do not skip human oversight for high-impact or autonomous workflows.
- Verify current official or organizational policy before platform-specific or regulated guidance.
- Escalate sensitive data, employee-impacting, customer-impacting, regulated, legal, privacy, security, finance, or public-facing AI use.
Deliverable Shape
For AI governance work, provide:
- Governance scope
- Checklist by domain
- Owners and evidence needed
- Pilot versus production gates
- Policy gaps
- Review cadence
- Escalation needs
References
- Read
references/ai-governance-checklist.mdwhen preparing AI governance checklists, policy controls, or rollout readiness reviews.
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.
- 12d ago First seen · 47 lines · 58 tokens per session scan A 5290de55c2ad
ai-governance-checklist is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 350 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 skills, from other repositories
authos-compliance-automation
Use AuthOS compliance and audit surfaces for privacy, SIEM, audit logs, risk events, MFA metrics, GDPR export, and anonymization. Use when implementing SAR export, right-to-be-forgotten flows, tenant SIEM streaming, audit review, or compliance evidence collection.
strm-mapping
Use when asked to map, crosswalk, align, compare, or gap-analyze any two cybersecurity frameworks, control catalogs, or regulatory requirements using NIST IR 8477 Set-Theory Relationship Mapping (STRM). Triggers on terms like "map controls", "crosswalk", "framework alignment", "gap analysis", or producing a STRM CSV…
huashu-takram-soft-tech
OpenDesign procurement & security leave-behind: the one-pager-plus a buying committee can forward and approve internally. Built as a decision-grade B2B sales deck for buying committee, security, procurement.
dependency-audit
Audits direct and transitive dependencies for license compliance, maintenance health, CVEs, abandoned packages, and bloat. Triggers on: "audit dependencies", "license check", "dependency health", "abandoned packages", "unused dependencies", "license compliance", "supply chain", "dependency risk".
boldsign-automation
Automate Boldsign tasks via Rube MCP (Composio). Always search tools first for current schemas.
kelly-legal-contracts
A review desk for business contracts such as non-disclosure agreements, service agreements, data-processing agreements, and statements of work. It compares clauses with a company's approved playbook and records review decisions.