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 AlexZio00/sovereign-skills --skill next-actiongit clone --depth 1 https://github.com/AlexZio00/sovereign-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/alexzio00/sovereign-skills/next-action)<a href="https://agentmods.dev/skills/alexzio00/sovereign-skills/next-action"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/next-action/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/alexzio00/sovereign-skills/next-action"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/next-action.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.00057 | $0.01305 |
| Opus 5 | $0.00028 | $0.00652 |
| Sonnet 5 | $0.00011 | $0.00261 |
| Haiku 4.5 | $0.00006 | $0.00130 |
Grade A, and why
next-action 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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/next — Next Action Recommender
Dominant Variable
Is the proposed action actually high-impact based on current project state? — it must come from measured files, not guesses.
Purpose
Reads current project state and proposes the top 3 next actions by impact. Different from stepback (direction check) — stepback asks "am I doing the right thing right now", this asks "what should I do next". Different from session-start (handoff load) — session-start restores the prior session, this recommends actions from current state.
Discard if: right after session start (session-start already loaded the handoff + output state). User already gave a specific task.
Key Assumptions
- Project has a CLAUDE.md — if broken: propose from git status alone (reduced scope).
- Is a git repository — if broken: propose from filesystem scan alone.
Trigger
/next- "what should I do next"
- "next action"
Workflow
Step 1: Collect State (parallel, 30s cap)
Read the following 5 sources. Skip missing files.
memory/session-handoff-LATEST.md— "What to do now" sectiongit status --short— uncommitted changed filesgit log --oneline -5— recent work flowtasks/lessons.md—conf≥0.7lessons stale 30+ days (need re-application)docs/STATE.mdor~/.claude/STATE.md— PENDING blockers
Step 2: Derive Candidates
Extract action candidates from collected data. Check each candidate's own underlying source for freshness (the specific lesson's seen date, the specific commit referenced) — not just whether the handoff file as a whole is old:
- Handoff "what to do now" → candidate as-is, but verify the specific file/commit it references is still current
- Uncommitted files → "commit + push" or "needs verification"
- PENDING blocker trigger satisfied → "resolve blocker"
- Stale lesson → "re-apply/verify lesson"
- git log pattern → "continue ongoing work" or "pivot direction"
Step 3: Sort by Impact
Narrow candidates to 3. Sort criteria:
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.
- 4d ago Changed 67e15edcfd36
- 12d ago First seen · 124 lines · 57 tokens per session scan A edae6d116fe7
next-action is a skill published in the GitHub repository AlexZio00/sovereign-skills (129 stars, last pushed 5d ago), licensed MIT. It adds 57 tokens to every session and 1,305 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
use-workflow-tdd-cycle
A test-first coding process based on TDD, or test-driven development: write a failing test, make it pass, then improve the code.
challenge
A two-phase decision check for testing whether a problem is real and whether a proposed idea is useful. It examines evidence, asks about only high-impact irreversible choices, and ends with a GO or NO-GO decision.
fix
A quick bug-fixing workflow for problems that can be safely corrected in one to three files. It also accepts an existing issue number or a finding from an audit.
nobrainer-review
Use when the owner says nb-review, deep-audit, deep-code-review, or deep-autoreview; explicitly requests an evidence-gated CLOSEOUT, adversarial BUGHUNT or RELEASEGATE; or needs final findings filtered to verified actionable defects. Use nobrainer-build for ordinary implementation and correction work.
PR Description Writer
Writes clear, thorough pull request descriptions from a diff or list of changes.
nobrainer-sessions
Use when the owner says nb-sessions, nb-multi, or session-handoff, or asks for visible named reusable multi-session work with exact identity, isolated write scopes, audited handoffs, recovery, or controlled parallelism; do not use for a coherent one-session task.