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 MageByte-Zero/spec-superflow --skill need-explorergit clone --depth 1 https://github.com/MageByte-Zero/spec-superflowWrote 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/magebyte-zero/spec-superflow/need-explorer)<a href="https://agentmods.dev/skills/magebyte-zero/spec-superflow/need-explorer"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/need-explorer/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/magebyte-zero/spec-superflow/need-explorer"><img src="https://agentmods.dev/badge/skills/magebyte-zero/spec-superflow/need-explorer.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.00044 | $0.00724 |
| Opus 5.5 | $0.00018 | $0.00290 |
| Sonnet 5.5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
need-explorer 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 24d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Need Explorer
Bundled runtime
Before executing a CLI line below, replace its leading SSF with node "<plugin-root>/scripts/spec-superflow.mjs"; <plugin-root> is the absolute directory two levels above this file. Never run SSF literally or call an ssf from PATH.
Turn a rough idea into a stable change definition before writing artifacts.
Primary Goal
Agree on: problem, scope, non-goals, success criteria, whether to split before specification.
Process
1. Inspect Context First
Before asking questions, understand what exists and what constraints are in place.
2. One Question at a Time
Ask a single clear question, wait for the answer, digest, then ask the next. Never ask 3+ questions at once. Each answer informs the next question.
3. Prefer Multiple-Choice Questions
Present 2-3 options when reasonable answers are finite. This reduces cognitive load and surfaces unconsidered choices.
4. Propose 2-3 Approaches with Trade-Offs
For each approach: what it is, upside, downside, best-for. Then recommend one and explain why. Never present a single path — always name at least one alternative.
5. Validate Before Concluding
Restate what you heard: "Here's what I'm hearing: [problem, scope, non-goals, success criteria]. Does this match?" Incorporate corrections and re-validate.
6. DP-1: Requirement Confirmation Gate
After user confirms the summary:
SSF state set <change-dir> dp_1_result "confirmed: <one-line summary>"
SSF state set <change-dir> dp_1_timestamp now
DP-1 confirms scope, non-goals, and success criteria before artifact creation.
7. Hand Off
Once DP-1 is recorded, hand off to spec-writer.
Anti-Patterns
- Skipping exploration: "Simple" changes have scope too. Five minutes of exploration prevents two hours of rework.
- Proposing solutions before clarifying: If the user says "add caching," first ask what problem caching solves.
- Exploring indefinitely: Stop when change name, problem statement, scope, non-goals, success criteria, and decomposition decision are all clear.
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.
- 24d ago Changed · +4 lines c299a3b6015b
- 26d ago Changed · -33 lines 23345e8832e6
- 1mo ago Changed 8bd0d52075f9
- 1mo ago First seen · 107 lines · 44 tokens per session scan A 8d4f8d5c0179
need-explorer is a skill published in the GitHub repository MageByte-Zero/spec-superflow (867 stars, last pushed 16d ago), licensed MIT. It adds 44 tokens to every session and 724 once invoked, about $0.0002 per session on Opus 5.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
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
acceptance-test-authoring
Use when creating or modifying acceptance tests, configuring cucumber-js or behave runners, writing or refactoring step definitions, linting executable Gherkin specs, choosing an acceptance stack, or implementing OpenSpec tasks that involve acceptance tests.
openspec-bulk-apply-change
Use when multiple active OpenSpec changes should be applied concurrently in isolated worktrees with delegated verification and no merge.
task-to-pr
Delivers specs or decided tasks as tested, independently reviewed pull requests. Runs the CI and review repair loop, then leaves passing pull requests open unless merging was explicitly authorized.
factory
Delivers a spec or decided task through the task-to-pr workflow and merges after all quality and approval gates pass. Explicit invocation grants merge authority for the supplied work.