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 opendatahub-io/ai-helpers --skill module-compliancegit clone --depth 1 https://github.com/opendatahub-io/ai-helpersWrote 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/opendatahub-io/ai-helpers/module-compliance)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/module-compliance"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/module-compliance/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/opendatahub-io/ai-helpers/module-compliance"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/module-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00700 |
| Opus 5 | $0.00029 | $0.00350 |
| Sonnet 5 | $0.00012 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
module-compliance 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ODH Module Compliance Check
Validate a module operator repository against the ODH platform contract.
Step 1: Identify the module root
If $ARGUMENTS provides a path, use it. Otherwise use the current working
directory.
Verify the directory contains a Go module by checking for go.mod. Read
go.mod and confirm it imports
github.com/opendatahub-io/odh-platform-utilities at version v0.1.0 or
later. If the import is missing, record a CRITICAL finding immediately --
the module must use the shared library, not the operator internal types.
Locate the CRD types directory by searching for files matching
api/**/types.go or api/**/*_types.go. Locate the controller directory by
searching for files matching internal/controller/**/*.go.
Step 2: Run compliance checks
Load the full rule set from ${CLAUDE_SKILL_DIR}/references/contract.md.
For each rule, search the codebase using Grep and Read to determine
pass/fail. Collect results into a list with rule ID, status (PASS / FAIL /
WARN / SKIP), file path and line number for violations, and a short
explanation.
Rules are grouped into these categories:
- API contract -- PlatformObject interface, status fields, mandatory conditions, singleton enforcement, API group and version.
- Spec conventions -- CommonSpec pattern, ManagementSpec, platform-managed fields, ConfigMap minimality.
- Controller patterns -- Reconciler builder, GC action ordering, condition manager setup, dependency handling, observedGeneration.
- Helm chart -- Controller-only manifests, no application resources.
- Security & metadata -- Webhook ownership, cert-manager TLS, metadata labels/annotations, RBAC scoping.
- Separation of concerns -- No orchestrator logic, self-contained module.
Step 3: Report findings
Present results grouped by category. Use this format:
## Module Compliance Report: <module-name>
### API Contract
- [PASS] MC-01 PlatformObject interface implemented
- [FAIL] MC-02 Missing WithReleases implementation (api/v1alpha1/types.go:42)
→ Add GetReleaseStatus() and SetReleaseStatus() methods
### Spec Conventions
...
### Summary
Total: 18 rules checked
Passed: 15
Failed: 2
Warnings: 1
What ships with it
7 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 · 83 lines · 58 tokens per session scan A 5813c44218f7
module-compliance is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 5d ago), licensed Apache-2.0. It adds 58 tokens to every session and 700 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-30.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
docker-patterns
Docker and Docker Compose patterns for local development, container security, networking, volume strategies, and multi-service orchestration.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.