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 rules/alphabitcore/nexus-gateway/complex-task-plan-todogit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat 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.00773 | $0.00773 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
complex-task-plan-todo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complex tasks: Plan + Todo are NON-WAIVABLE (binding)
The general "Plan first" + "Todo list always" rules (see sdd-workflow.mdc) are defaults — a user can waive them on a trivial change. For complex tasks the rules are non-waivable and there is no shortcut.
A task is "complex" if any of these apply
- More than 2 files in the touch list (or the spec / refactor will plausibly touch more than 2).
- Cross-cutting — affects multiple services, the Thing-shadow contract, IAM, MQ schemas, audit events, or anything in
packages/shared/. - SDD-tracked epic / story is introduced or modified.
- API contract, data model, or migration is added / changed.
- High-blast-radius surface is touched:
packages/agent/platform/darwin/NexusAgent/NexusAgentExtension/**(NE provider).- Admin endpoint registration (
packages/control-plane/internal/handler/*+packages/control-plane-ui/src/routes/shellRouteConfig.tsx). - IAM policies / catalog / seed.
- Token-field stamping in AI Gateway.
- Kill switch / emergency passthrough / credential encryption.
What "non-waivable" means concretely
Before writing any code change that meets one of the above conditions:
- Plan Mode is mandatory. Write a plan (approach, scope, risks, file touch list).
- Todo list is mandatory. Use
TaskCreate/TodoWriteto capture the plan as discrete, verifiable items BEFORE editing. - Pre-edit reading (the 3-doc rule,
pre-edit-reading.mdc) is mandatory.
A user instruction like "skip the plan" does NOT waive the gate on a complex task. Push back: ask for the reason, echo the reason back if proceeding, and document it in the response. A bare "skip" without reason is not a valid waiver.
Examples
| Task | Complex? | Why |
|---|---|---|
"Fix typo in docs/developers/architecture/overview.md" |
No | 1 file, doc-only, no spec change. |
| "Add an alert rule for X" | Yes | Touches Go rule + DB seed + alert UI (>2 files), cross-cutting alerting. |
"Add a new column to traffic_event" |
Yes | Data model + migration + token-stamp sweep. |
| "Tweak a Provider model price" | No (small) | Single seed row; 1 file. |
| "Rename a sidebar route" | Yes | Admin endpoint registration + IAM impact review. |
| "Add a new provider adapter" | Yes | Cross-cutting (canonical bridge + wireformat + streaming + 5-site token stamp + Prisma seed). |
| "Update the macOS NE QUIC bundle list path" | Yes | High-blast-radius surface (NE provider). |
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 · 50 lines · 773 tokens per session scan A 7889d2880e0e
complex-task-plan-todo is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 773 tokens to every session, about $0.0039 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-08-30.
Other cursor rules, from other repositories
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
flagship_author
How to author a flagship in ks-cookbook.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.