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/implement-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.00740 |
| Opus 5 | $0.00000 | $0.00370 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
implement-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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Implementation Process
Now that we have a spec and tasks list ready for implementation, we will proceed with implementation of this spec by following this multi-phase process:
PHASE 1: Determine which task group(s) from tasks.md should be implemented PHASE 2: Delegate implementation to the implementer subagent PHASE 2.5: Simplify modified code PHASE 3: After ALL task groups have been implemented, delegate to implementation-verifier to produce the final verification report.
Follow each of these phases and their individual workflows IN SEQUENCE:
Multi-Phase Process
PHASE 1: Determine which task group(s) to implement
First, check if the user has already provided instructions about which task group(s) to implement.
If the user HAS provided instructions: Proceed to PHASE 2 to delegate implementation of those specified task group(s) to the implementer subagent.
If the user has NOT provided instructions:
Read agent-os/specs/[this-spec]/tasks.md to review the available task groups, then output the following message to the user and WAIT for their response:
Should we proceed with implementation of all task groups in tasks.md?
If not, then please specify which task(s) to implement.
PHASE 2: Delegate implementation to the implementer subagent
Use the Task tool with subagent_type: "implementer" to spawn the implementer subagent.
In the Task prompt, provide:
- The specific task group(s) from
agent-os/specs/[this-spec]/tasks.mdincluding the parent task, all sub-tasks, and any sub-bullet points - The path to this spec's documentation:
agent-os/specs/[this-spec]/spec.md - The path to this spec's requirements:
agent-os/specs/[this-spec]/planning/requirements.md - The path to this spec's visuals (if any):
agent-os/specs/[this-spec]/planning/visuals
Instruct the subagent to:
- Analyze the provided spec.md, requirements.md, and visuals (if any)
- Analyze patterns in the codebase according to its built-in workflow
- Implement the assigned task group according to requirements and standards
- Update
agent-os/specs/[this-spec]/tasks.mdto mark completed tasks with- [x]
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 · 72 lines · 0 tokens per session scan A e8a98ec6ee04
implement-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 740 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.