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 stark-ai-de/agent-skills --skill skill-repo-curatorgit clone --depth 1 https://github.com/stark-ai-de/agent-skillsWrote 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/stark-ai-de/agent-skills/skill-repo-curator)<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/skill-repo-curator"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/skill-repo-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.
<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/skill-repo-curator"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/skill-repo-curator.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.00054 | $0.00869 |
| Opus 5 | $0.00027 | $0.00434 |
| Sonnet 5 | $0.00011 | $0.00174 |
| Haiku 4.5 | $0.00005 | $0.00087 |
Grade A, and why
skill-repo-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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Repo Curator
Goal
Keep a public Agent Skills repository coherent, installable, safe, and ready for users who install skills through npx skills.
When to use
- The user asks to maintain or release a skills repository.
- The README catalog may not match the
skills/tree. - Validation, deprecation, publishing, or install commands need review.
When not to use
- The user wants to write a single skill; use
skill-authoring-review. - The user wants install help only; use
skill-installation-support. - The repository is not a skills repository and needs a general audit; use
repo-health-audit.
Inputs
skills/**/SKILL.mdREADME.md,CHANGELOG.md,CONTRIBUTING.md,SECURITY.md, andLICENSEpackage.json, validation scripts, and CI workflows- Output from
npm run validate,npm run list, and the localnpx skillsdiscovery command.
Inputs to inspect
- Inspect the skill tree, catalog docs, validation scripts, ignored local helper installs, and install smoke-test output.
- Check that upstream helper skills are installed project-locally rather than vendored into the public catalog.
Process
- Inspect the skill tree and top-level repository files.
- Run the local validation and listing commands when possible.
- Compare README catalog entries against discovered skills.
- Check install commands for
<github-owner>/<repo>placeholders or final repository coordinates. - Review changelog and release checklist when preparing a release.
- Apply deprecation policy before removing or replacing a skill.
- Report the exact validation status, drift, and next action.
Workflow
Follow the process above, fix structural drift first, then update catalog, changelog, and release notes.
Decision points
- If a skill is obsolete, prefer deprecation over deletion.
- If README and skill tree disagree, update the catalog or explain why the skill is intentionally hidden.
- If validation fails, fix structural errors before content polish.
- If project-local helper skills exist under
.agents/skills/, usenpx skills@latest add ./skills --listfor local discovery so helper skills do not mask the publishable catalog.
What ships with it
3 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 · 105 lines · 54 tokens per session scan A ed8ee45b1792
skill-repo-curator is a skill published in the GitHub repository stark-ai-de/agent-skills (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 869 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
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-implement-story
Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.
openlore-write-tests
Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.