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-migrategit 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-migrate)<a href="https://agentmods.dev/skills/opendatahub-io/ai-helpers/module-migrate"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/module-migrate/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-migrate"><img src="https://agentmods.dev/badge/skills/opendatahub-io/ai-helpers/module-migrate.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.00065 | $0.02179 |
| Opus 5 | $0.00032 | $0.01090 |
| Sonnet 5 | $0.00013 | $0.00436 |
| Haiku 4.5 | $0.00006 | $0.00218 |
Grade A, and why
module-migrate 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ODH Module Migration
Analyze an in-tree ODH operator component and generate a migration checklist for extracting it into a standalone module operator.
Prerequisites
The user must have the opendatahub-io/opendatahub-operator repository (or a
fork) checked out locally. This skill reads that codebase to analyze the
component.
Step 1: Identify the component
Extract the component name from $ARGUMENTS. If not provided, ask the user.
Search for the component in these locations within the operator repo:
internal/controller/components/<name>/(component controllers)internal/controller/services/<name>/(service controllers)api/components/v1alpha1/<name>_types.go(component CRD types)api/services/v1alpha1/<name>_types.go(service CRD types)
If the component is found under components/, the target API group is
components.platform.opendatahub.io. If under services/, use
services.platform.opendatahub.io.
Step 2: Analyze controller logic
Read all files in the component's controller directory. Document:
- Handler implementation -- the file implementing the handler interface (ComponentHandler or ServiceHandler). Note which interface methods are implemented.
- Controller setup -- how the reconciler is registered. Note if it uses the builder pattern or a legacy pattern.
- Action functions -- list each action (render, deploy, gc, custom) and what it does.
- Resources managed -- grep for resource kinds the controller creates/updates (Deployments, Services, ConfigMaps, Routes, etc.).
- Embedded manifests -- look for
go:embeddirectives, template files, or inline YAML strings. Note their locations. - Platform dependencies -- grep for references to DSCI, DSC, or other platform CRs within the controller logic.
Step 3: Analyze CRD types
Read the component's CRD types file. Document:
- Spec fields -- list all spec fields. Identify which are user-facing (belong in CommonSpec) vs operator-written (stay in Spec only).
- Status fields -- check if it already implements PlatformObject or uses a different status pattern.
- Platform-managed fields -- fields populated by the orchestrator (auth, certs, monitoring config).
- Validation -- CEL rules, webhook validations, enum constraints.
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 · 237 lines · 65 tokens per session scan A 61f7380a9de0
module-migrate is a skill published in the GitHub repository opendatahub-io/ai-helpers (37 stars, last pushed 2d ago), licensed Apache-2.0. It adds 65 tokens to every session and 2,179 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.
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.
spark-training-gotchas
Preflight and diagnose the ten known failure modes for ML training on NVIDIA DGX Spark. Use when a training run on DGX Spark fails to start, OOMs below the 128GB limit, slows down mid-run, or before any multi-hour training job on GB10.
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…