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/create-tasksgit clone --depth 1 https://github.com/adawalli/nexusWhat 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.00399 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
create-tasks 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 2d 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
Task List Creation Process
You are creating a tasks breakdown from a given spec and requirements for a new feature.
PHASE 1: Get and read the spec.md and/or requirements document(s)
You will need ONE OR BOTH of these files to inform your tasks breakdown:
agent-os/specs/[this-spec]/spec.mdagent-os/specs/[this-spec]/planning/requirements.md
IF you don't have ONE OR BOTH of those files in your current conversation context, then ask user to provide direction on where to you can find them by outputting the following request then wait for user's response:
I'll need a spec.md or requirements.md (or both) in order to build a tasks list.
Please direct me to where I can find those. If you haven't created them yet, you can run /shape-spec or /write-spec.
PHASE 2: Create tasks.md
Once you have spec.md AND/OR requirements.md, use the tasks-list-creator subagent to break down the spec and requirements into an actionable tasks list with strategic grouping and ordering.
Provide the tasks-list-creator:
agent-os/specs/[this-spec]/spec.md(if present)agent-os/specs/[this-spec]/planning/requirements.md(if present)agent-os/specs/[this-spec]/planning/visuals/and its' contents (if present)
The tasks-list-creator will create tasks.md inside the spec folder.
PHASE 3: Inform user
Once the tasks-list-creator has created tasks.md output the following to inform the user:
Your tasks list ready!
✅ Tasks list created: `agent-os/specs/[this-spec]/tasks.md`
NEXT STEP 👉 Run `/implement-tasks` (simple, effective) or `/orchestrate-tasks` (advanced, powerful) to start building!
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.
- 2d ago First seen · 43 lines · 0 tokens per session scan A 6a3c48ee84c3
create-tasks is a command published in the GitHub repository adawalli/nexus (23 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 399 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.