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 agentmods add skills/sd0xdev/sd0x-harness/next-stepnpx skills add sd0xdev/sd0x-harness --skill next-stepgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/next-step)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/next-step"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/next-step.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.01559 |
| Opus 5 | $0.00032 | $0.00779 |
| Sonnet 5 | $0.00013 | $0.00312 |
| Haiku 4.5 | $0.00006 | $0.00156 |
Grade A, and why
next-step 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 yesterday.
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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Step Advisor
When NOT to Use
- Auto-loop already handling review/precommit flow (hooks track and assist)
- User gave a clear, specific instruction (just do it)
- Mid-execution of a skill workflow (follow that skill's progression)
Procedure
- Run
bash scripts/run-skill.sh next-step analyze.jsto collect deterministic findings - Parse the JSON output — findings, gates, diff summary, phase, feature_context, next_actions, backlog
- If P0/P1 findings exist → format top 3 as actionable suggestions (Findings Mode)
- If mid-pipeline (gates not all passed, no P0/P1) → use progression tables to suggest next step
- If phase = post_precommit → suggest doc sync + request update (use next_actions)
- If phase = feature_complete → output feature complete summary with backlog
- If all gates pass and no P0/P1 → output session summary with commit seed (Summary Mode, P2/P3 shown as oversights)
Script Integration
The analyze script runs 18 deterministic heuristics against git state, review state, and feature context:
| Priority | Heuristics | Meaning |
|---|---|---|
| P0 | Gate missing (code review, doc review, precommit) | Required steps not completed |
| P1 | Test gap, security hotspot, migration risk, doc-sync-needed, request-stale, corpus-unreadable | Important oversights |
| P2 | README missing, skill-lint needed, locale drift, mixed concerns, ac-incomplete, intent-advisory (planning docs without exact intent-.md) | Quality improvements |
| P3 | Main branch warning, requirements-advisory, feature-complete | Informational |
The script exits with code 0 (no P0/P1), 1 (has P1), or 2 (has P0).
Output Fields (v2)
| Field | Type | Description |
|---|---|---|
| phase | string | mid_development / post_precommit / ready_to_commit / feature_complete / clean |
| feature_context | object | { key, source, confidence, docs_path, has_tech_spec, has_requirements, has_requests } |
| next_actions | array | [{ id, command, args, reason, confidence }] sorted by confidence desc |
| backlog | object/null | { total_features, incomplete_features } — only when phase = feature_complete |
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.
- yesterday First seen · 156 lines · 63 tokens per session scan A b8fc41d2b49c
next-step is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,559 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-09-03.
Other skills, from other repositories
cc10x-router
THE ONLY ENTRY POINT FOR CC10X. Activate this skill for build, debug, review, and plan requests. Use when the user asks to implement, fix, review, plan, test, refactor, or continue code work. Trigger keywords: build, implement, create, write, add, review, audit, debug, fix, error, bug, broken, plan, design, architect…
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.