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 allemaar/open-skills --skill next-skillsgit clone --depth 1 https://github.com/allemaar/open-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/allemaar/open-skills/next-skills)<a href="https://agentmods.dev/skills/allemaar/open-skills/next-skills"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/next-skills/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/allemaar/open-skills/next-skills"><img src="https://agentmods.dev/badge/skills/allemaar/open-skills/next-skills.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.00097 | $0.01585 |
| Opus 5 | $0.00048 | $0.00792 |
| Sonnet 5 | $0.00019 | $0.00317 |
| Haiku 4.5 | $0.00010 | $0.00159 |
Grade A, and why
next-skills 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next-skills
Next Skills (NSP) answers the question a skill leaves open: what now? When a participating skill finishes, NSP reads that skill's declared successors and surfaces them — each with an activation phrase and a short reason — for the caller to choose from. The caller (a human, or another agent) picks; nothing auto-runs.
NSP is invoked two ways: automatically, when a skill carrying the NSP opt-in block completes;
or directly, as /next-skills <skill> to preview a skill's declared successors.
Structured execution spec:
protocol.yon. It carries the three steps and the offer-only / empty-silent / loop-safe rules as validatable records; this file is the explanation. Keep the two in sync — edit one, update the other and refresh the@STAMPdate.
The protocol — three steps
- Read. Take the just-finished skill's
next-skills:front-matter list. Each entry has askill, aphrase(its activation phrase), and awhy(one line: why it might be useful next). If the list is absent or empty, stop silently — NSP surfaces nothing. - Surface. Present the recommendations for the caller to pick (runtime-mapped, below). Recommendations are offered, never auto-invoked.
- Activate. On the caller's pick, activate the chosen skill(s) via their activation phrase. On no pick, end quietly.
Surface step — runtime mapping
- Claude Code →
AskUserQuestion(multiSelect). One option per recommendation: the label is the skill name, the description is itswhy. The user may pick one, several, or none ("Other" / dismiss always declines). - Codex, or any runtime without a structured-question tool → present a numbered prose list,
each line
N. <phrase> — <why>, and wait for the caller's reply.
The Read and Activate steps are runtime-agnostic.
Data contract
The next-skills: front-matter field on a participating skill is canonical:
next-skills:
- skill: insight-assess
phrase: "/assess"
why: "Evaluate the options you just generated and pick one"
What ships with it
1 file 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 · 137 lines · 97 tokens per session scan A 67675b98f7b8
next-skills is a skill published in the GitHub repository allemaar/open-skills (14 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 1,585 once invoked, about $0.0005 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
polis-protocol
Set up and run a self-improving, multi-vendor AI agent team with the Polis Protocol — a markdown polis/ folder where each agent is a citizen with a capability card, tasks are contracts routed to whoever has the best track record by a learning router, settled work files lessons that compound into team memory, and…
media
Skill "media" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
_data
Skill "_data" from ymxlx/polis-protocol, covering polis protocol: a self-optimizing city of agents, the core idea, when this skill is active, structure of a polis and the first thing to do every session.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.