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 DorianSchlede/nexus-template --skill plan-buildgit clone --depth 1 https://github.com/DorianSchlede/nexus-templateWrote 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/dorianschlede/nexus-template/plan-build)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/plan-build"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/plan-build.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.1 | $0.00019 | $0.05393 |
| Opus 5 | $0.00010 | $0.02697 |
| Sonnet 5 | $0.00004 | $0.01079 |
| Haiku 4.5 | $0.00002 | $0.00539 |
Grade A, and why
plan-build 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 7d 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 — 714 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboarding Awareness (CHECK BEFORE STARTING)
Before creating a build, AI MUST check user-config.yaml for incomplete onboarding:
Pre-Flight Check (MANDATORY)
# Check learning_tracker.completed in user-config.yaml
learn_builds: false → SUGGEST 'learn builds' skill FIRST
If learn_builds: false AND this is user's FIRST build:
Before creating your first build, would you like a quick 8-minute tutorial
on how Nexus builds work? It covers:
- When to use builds vs skills (avoid common mistakes)
- Build structure and lifecycle
- How to track progress effectively
Say 'learn builds' to start the tutorial, or 'skip' to create directly.
If user says 'skip': Proceed with build creation but add this note at the end:
Tip: Run 'learn builds' later if you want to understand the build system deeply.
If learn_builds: true: Proceed normally without suggestion.
MANDATORY ROUTER PATTERN
plan-build is the ONLY entry point for all build creation.
WORKFLOW SEQUENCE (DO NOT SKIP STEPS)
- TYPE DETECTION → Semantic match from _type.yaml descriptions
- BUILD SETUP → Run init_build.py with detected type
- DISCOVERY → 3-phase flow (inline) OR skill-based 3a. Discovery Questions → Understand what user wants to build 3b. Active Research → AI explores based on answers 3c. Informed Follow-ups → Questions + optional follow-up research ↳ Loop to 3b if new areas discovered (max 2 loops)
- MENTAL MODELS → MANDATORY - Run AFTER discovery
- RE-DISCOVERY → If mental models reveal gaps (max 2 rounds)
- FINALIZATION → Fill 03-plan.md, fill 04-steps.md
CRITICAL CHECKPOINTS:
- After Phase 3: plan.md MUST have success criteria + risks (from mental models)
- After Phase 6: plan.md MUST be filled (not template), steps.md MUST have concrete tasks
Critical Rules
What ships with it
51 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/active-discovery-guide.md 20 KB
- references/build-schema.yaml 1.7 KB
- references/build-types.md 9.8 KB
- references/ears-patterns.md 3.4 KB
- references/incose-rules.md 3.9 KB
- references/routing-logic.md 3.0 KB
- references/workflows.md 1.2 KB
- scripts/create-build.py 9.0 KB runs code
- scripts/init_build.py 18 KB runs code
- scripts/templates/template-build.md 422 B
- scripts/templates/template-content.md 366 B
- scripts/templates/template-generic.md 0 B
- scripts/templates/template-process.md 521 B
- scripts/templates/template-research.md 354 B
- scripts/templates/template-strategy.md 448 B
- templates/types/content/_type.yaml 530 B
- templates/types/content/discovery.md 2.7 KB
- templates/types/content/overview.md 657 B
- templates/types/content/plan.md 999 B
- templates/types/content/steps.md 1.7 KB
- templates/types/generic/_type.yaml 513 B
- templates/types/generic/discovery.md 1.7 KB
- templates/types/generic/overview.md 450 B
- templates/types/generic/plan.md 586 B
- templates/types/generic/steps.md 1.1 KB
- templates/types/integration/_type.yaml 767 B
- templates/types/integration/discovery.md 1.4 KB
- templates/types/integration/overview.md 675 B
- templates/types/integration/plan.md 1.6 KB
- templates/types/integration/steps.md 1.9 KB
- templates/types/process/_type.yaml 534 B
- templates/types/process/discovery.md 3.3 KB
- templates/types/process/overview.md 718 B
- templates/types/process/plan.md 1.2 KB
- templates/types/process/steps.md 1.8 KB
- templates/types/research/_type.yaml 651 B
- templates/types/research/discovery.md 1.7 KB
- templates/types/research/overview.md 664 B
- templates/types/research/plan.md 1.5 KB
- templates/types/research/steps.md 1.9 KB
- templates/types/skill/_type.yaml 589 B
- templates/types/skill/discovery.md 4.2 KB
- templates/types/skill/overview.md 844 B
- templates/types/skill/plan.md 1.7 KB
- templates/types/skill/steps.md 2.8 KB
- templates/types/strategy/_type.yaml 550 B
- templates/types/strategy/discovery.md 3.3 KB
- templates/types/strategy/overview.md 662 B
- templates/types/strategy/plan.md 1.3 KB
- templates/types/strategy/steps.md 1.6 KB
- TEST-REPORT-init_build.md 12 KB
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.
- 7d ago First seen · 714 lines · 19 tokens per session scan A 156fa147791a
plan-build is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 19 tokens to every session and 5,393 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…