Borrowing it
Nothing to install: this file belongs to ai4curation/ai-gene-review. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ai4curation/ai-gene-review/main/.claude/skills/module-curation/SKILL.mdgit clone --depth 1 https://github.com/ai4curation/ai-gene-reviewWrote 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/ai4curation/ai-gene-review/module-curation)<a href="https://agentmods.dev/skills/ai4curation/ai-gene-review/module-curation"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/module-curation/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/ai4curation/ai-gene-review/module-curation"><img src="https://agentmods.dev/badge/skills/ai4curation/ai-gene-review/module-curation.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.00061 | $0.00937 |
| Opus 5 | $0.00030 | $0.00468 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
module-curation 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Module Curation
Use this skill for modules/*.yaml work and for project pages that describe
module/pathway curation. The goal is a reusable, defensible biological module,
not a flat list of annotations or a species-specific note disguised as a module.
Workflow
- Read the local context before editing:
modules/README.md- the target
modules/<module>.yaml - any adjacent
<module>-deep-research-*.md - related
projects/**batch page(s), if the task is pathway-batch work - relevant gene reviews and UniProt/GOA files for concrete members
- Decide the module boundary before filling YAML:
- What biological process, complex, reaction chain, or reusable motif is the module?
- Which genes/proteins are core members, and which are activation context, substrate supply, regulation, upstream/downstream biology, or separate modules?
- Is this a concrete species/pathway instance or an abstract reusable motif?
- Does the boundary have at least two substantive parts/roles/steps? If it
collapses to one gene, one enzyme, or one reaction, do not create or retain
a standalone
ModuleReview; record it as pathway/gene curation and fold it into a broader module later.
- Model the structure:
- Put module-level process/complex/context terms on
module.conceptsandmodule.context. - Put molecular functions on leaf
annotons[].function, not on a biological-process module just because the member protein has that MF. - Use
partsfor required steps or roles,variant_setsfor alternatives, andconnectionsfor ordered/causal links.
- Put module-level process/complex/context terms on
- Ground claims with checkable provenance:
- Use exact UniProt, GO, Rhea, ChEBI, PANTHER
PTHR, and PAINTPTNids. - Never guess PTNs or identifiers. Resolve PTNs from local PANTHER/PAINT data or GOA WITH/FROM evidence.
- Use representative members to orient family-level claims without turning a reusable module into a species-specific member list.
- Use exact UniProt, GO, Rhea, ChEBI, PANTHER
- Validate and render before committing:
uv run linkml-validate -s src/ai_gene_review/schema/gene_review.yaml -C ModuleReview modules/<module>.yamluv run python -m ai_gene_review.validation.module_validator modules/<module>.yamljust render-module modules/<module>.yaml- render any touched project page with
uv run ai-gene-review render-projects ... - run
git diff --check
What ships with it
4 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 · 76 lines · 61 tokens per session scan A c67d890721b4
module-curation is a skill published in the GitHub repository ai4curation/ai-gene-review (24 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 61 tokens to every session and 937 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
dosdp-design-patterns
Skills for understanding and applying DOSDP (Dead Simple Ontology Design Patterns) to ensure consistent ontology term creation and maintenance. This skill is about recognizing patterns and ensuring consistency, not using dosdp-tools directly.
robot-obo-tool
Skills for using ROBOT, the OBO ontology command-line toolkit for reasoning, template-based term creation, quality control, format conversion, and ontology manipulation. Use this when working with OWL/OBO ontologies that need automated processing.
editing-obo-ontologies
Skills and tools for editing OBO format ontologies, including querying terms, checking out/checking in individual terms, and following OBO format conventions. Do not use this if the source for the ontology you are editing is not in obo format (e.g. ofn).
ontology-access-kit
Skills for querying ontologies using the Ontology Access Kit (OAK). This should only be used for complex ontology operations, for basic external ontology searching use the OLS MCP.
cuopt-numerical-optimization-formulation
LP, MILP, QP — concepts, problem-text parsing, and formulation patterns (parameters, constraints, decisions, objective). Concepts only; no API.
earth2studio-create-datasource
Create and validate Earth2Studio data source wrappers (DataSource, ForecastSource, DataFrameSource, ForecastFrameSource) from remote stores. Do NOT use for fetching data with existing sources, model inference, or installation tasks.