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 commands/adawalli/nexus/plan-productgit clone --depth 1 https://github.com/adawalli/nexusWrote 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/commands/adawalli/nexus/plan-product)<a href="https://agentmods.dev/commands/adawalli/nexus/plan-product"><img src="https://agentmods.dev/badge/commands/adawalli/nexus/plan-product.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.00000 | $0.00356 |
| Opus 5 | $0.00000 | $0.00178 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
plan-product 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 5d 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.
What it actually says
Product Planning Process
You are helping to plan and document the mission, roadmap and tech stack for the current product. This will include:
- Gathering Information: The user's product vision, user personas, problems and key features
- Mission Document: Take what you've gathered and create a concise mission document
- Roadmap: Create a phased development plan with prioritized features
- Tech stack: Establish the technical stack used for all aspects of this product's codebase
This process will create these files in agent-os/product/ directory.
PHASE 1: Gather Product Requirements
Use the product-planner subagent to create comprehensive product documentation.
IF the user has provided any details in regards to the product idea, its purpose, features list, target users and any other details then provide those to the product-planner subagent.
The product-planner will:
- Confirm (or gather) product idea, features, target users, confirm the tech stack and gather other details
- Create
agent-os/product/mission.mdwith product vision and strategy - Create
agent-os/product/roadmap.mdwith phased development plan - Create
agent-os/product/tech-stack.mddocumenting all of this product's tech stack choices
PHASE 2: Inform the user
After all steps are complete, output the following to inform the user:
Your product planning is all set!
✅ Product mission: `agent-os/product/mission.md`
✅ Product roadmap: `agent-os/product/roadmap.md`
✅ Product tech stack: `agent-os/product/tech-stack.md`
NEXT STEP 👉 Run `/shape-spec` or `/write-spec` to start work on a feature!
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.
- 5d ago First seen · 38 lines · 0 tokens per session scan A 3bd49770a44b
plan-product is a command published in the GitHub repository adawalli/nexus (23 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 356 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.