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 execute-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/execute-build)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/execute-build"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/execute-build/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/execute-build"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/execute-build.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01642 |
| Opus 5.5 | $0.00009 | $0.00657 |
| Sonnet 5.5 | $0.00005 | $0.00328 |
| Haiku 4.5 | $0.00002 | $0.00164 |
Grade A, and why
execute-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 1mo 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Build
Execute build work systematically with progress tracking.
Workflow
1. Load Context
nexus-load --build [ID]
Read files from _usage.recommended_reads.
2. Show Status
----------------------------------
BUILD: [Name]
----------------------------------
Progress: [X]/[Y] tasks ([Z]%)
Current: Section [N] - [Name]
Next: [Task description]
----------------------------------
3. Find Current State
Parse steps.md for:
- First uncompleted section (
## Section/Phase N) - Next uncompleted task (
- [ ])
4. Execute Section
Work through tasks in current section. Show after each:
[OK] Task [N] complete!
5. Bulk-Complete Section
When section done:
nexus-bulk-complete --build [ID] --section [N] --no-confirm
6. Update Resume State
CRITICAL: After bulk-complete succeeds:
nexus-update-resume --build [ID] --section [N+1] --completed [total]
Key: Set current_section to NEXT section (not completed one).
7. Continue or Complete
- More sections → repeat from step 4
- User says "pause" → offer partial bulk-complete, trigger close-session
- 100% done → update status to COMPLETE (see below), suggest archive
8. Update Build Status (When Complete)
CRITICAL: Use Edit tool to update status: in 01-planning/01-overview.md.
Valid statuses ONLY: PLANNING, IN_PROGRESS, ACTIVE, COMPLETE, ARCHIVED
# In 01-overview.md frontmatter, change:
status: IN_PROGRESS
# To:
status: COMPLETE
NEVER use: EXECUTION, DONE, FINISHED, or any other value. These are invalid and will cause warnings.
Scripts Reference
bulk-complete.py
| Flag | Purpose |
|---|---|
--build ID |
Build ID (e.g., "05" or "05-name") |
--all |
Complete all tasks |
--section N |
Complete section N |
--tasks 1-5,7 |
Specific tasks |
--no-confirm |
Skip prompt (required for AI) |
Examples:
# Complete section 3
nexus-bulk-complete --build 05 --section 3 --no-confirm
# Complete specific tasks
nexus-bulk-complete --build 05 --tasks 1-10,15 --no-confirm
# Complete all
nexus-bulk-complete --build 05 --all --no-confirm
What ships with it
2 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.
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.
- 1mo ago First seen · 262 lines · 23 tokens per session scan A e5e614dc6a88
execute-build is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 8mo ago), licensed MIT. It adds 23 tokens to every session and 1,642 once invoked, about $0.0001 per session on Opus 5.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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…