skills-curator

skills-curator is a skill for Claude Code, Codex from regen-coordination/org-os-template. It costs 26 tokens per session (2,056 once invoked), scanned A, original, MIT.

A planning step that selects the right agent skills and libraries before starting a substantial project. It records the chosen tools and the reasons for using them.

In plain words
What is it for?
Use it before initiatives spanning multiple technical areas, or after a design has been approved and the implementation tools need to be selected.
Why use it?
It helps avoid choosing tools halfway through a project, which can cause rework and inconsistent implementation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md; mentions subagents; mentions Claude Code.

Good fit Use it before initiatives spanning multiple technical areas, or after a design has been approved and the implementation tools need to be selected.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/regen-coordination/org-os-template/skills-curator
Install

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.

Any agent
npx skills add regen-coordination/org-os-template --skill skills-curator
Clone the repo
git clone --depth 1 https://github.com/regen-coordination/org-os-template

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for skills-curator

README.md
[![agentmods](https://agentmods.dev/badge/skills/regen-coordination/org-os-template/skills-curator/github.svg)](https://agentmods.dev/skills/regen-coordination/org-os-template/skills-curator)
Your own site
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/skills-curator"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/skills-curator/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.

agentmods 80×15 button for skills-curator

Your own site · 80×15
<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/skills-curator"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/skills-curator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,056 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.02056
Opus 5 $0.00013 $0.01028
Sonnet 5 $0.00005 $0.00411
Haiku 4.5 $0.00003 $0.00206

Measured 8d ago against content hash 8074b0b57b5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

skills-curator 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 8d 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.

skills/skills-curator/SKILL.md · 222 lines

How it starts

The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skills Curator

When to Use

Before any non-trivial initiative. Specifically:

  • Before superpowers:writing-plans runs for an implementation plan that introduces new domains (frontend, design system, ML, data pipeline, etc.)
  • After superpowers:brainstorming produces a design spec
  • When an operator says "what skills should we use", "scope skills for", or asks for a "Phase 0"
  • When a new project crosses 2+ specialized domains and the agent stack hasn't been picked

Skip when:

  • The initiative is a routine task in an already-equipped project (no new domains)
  • The skill stack is locked by an existing convention (e.g., the project's CLAUDE.md mandates specific skills)

Why It Exists

Building well requires the right tools. Picking tools mid-build creates rework and inconsistency. Phase 0 separates deciding what to use from building with it — the same way that brainstorming separates deciding what to build from building it.

This skill produces a single artifact (docs/plans/YYYY-MM-DD-skills-curation.md) that any later phase can audit. It also creates a clean retrospective surface: at v1 of the initiative, every chosen skill gets a promote/improve/drop verdict against measured value.

Procedure

Step 1 — Read the design spec or brief

Read the initiative's design spec (typically at docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md) or the operator's brief. Extract:

  • Domains involved (e.g., frontend, design system, color, animation, accessibility, data pipeline, deploy, testing)
  • Tech stack constraints (e.g., Astro + React, vanilla, framework-locked)
  • Design surface needs (component library, color manipulation, motion, a11y)
  • Process needs (TDD, parallel agents, code review)

Step 2 — Identify candidate sources

Default sources to scan:

  • agentskills.io — community skill marketplace
  • skills.sh — skill marketplace
  • github.com/VoltAgent/awesome-design-md — design.md templates and design-system skills
  • github.com/anthropics/skills — official Anthropic skill catalog
  • Already-installed superpowers skills (process layer — usually already present)
  • Project-local skills at skills/, .agents/skills/, or instance equivalent

Read the full file on GitHub · 222 lines

Changes

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.

  1. 8d ago First seen · 222 lines · 26 tokens per session scan A 8074b0b57b5f

Subscribe to this mod's changes

skills-curator is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 2,056 once invoked, about $0.0001 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-09-03.