archive-build

archive-build is a skill for Claude Code, Codex from DorianSchlede/nexus-template. It costs 14 tokens per session (843 once invoked), scanned A, original, MIT.

A workflow for moving finished, cancelled, or paused software builds from an active folder into a completed-builds folder.

In plain words
What is it for?
It is for checking a build's status, confirming the move, archiving its files, and updating the build map.
Why use it?
It keeps the active build list focused while preserving older builds for later access.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: names the TodoWrite tool.

Good fit It is for checking a build's status, confirming the move, archiving its files, and updating the build map.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dorianschlede/nexus-template/archive-build
Install

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.

Any agent
npx skills add DorianSchlede/nexus-template --skill archive-build
Clone the repo
git clone --depth 1 https://github.com/DorianSchlede/nexus-template

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for archive-build

README.md
[![agentmods](https://agentmods.dev/badge/skills/dorianschlede/nexus-template/archive-build/github.svg)](https://agentmods.dev/skills/dorianschlede/nexus-template/archive-build)
Your own site
<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/archive-build"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/archive-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.

agentmods 80×15 button for archive-build

Your own site · 80×15
<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/archive-build"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/archive-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 843 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00843
Opus 5 $0.00007 $0.00421
Sonnet 5 $0.00003 $0.00169
Haiku 4.5 $0.00001 $0.00084

Measured 10d ago against content hash c338f9b0c46c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

archive-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 10d 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.

00-system/skills/builds/archive-build/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Archive Build

Move completed builds to the complete folder for a clean, focused build list.

Purpose

Archive builds that are:

  • 100% complete
  • Cancelled or on-hold
  • No longer active

Archived builds stay accessible in 02-builds/complete/ but don't clutter your active list.


Workflow

Step 1: Initialize TodoList

Create TodoWrite with all workflow steps:

- [ ] Identify build to archive
- [ ] Load and verify build status
- [ ] Confirm archive action
- [ ] Move build to complete
- [ ] Update build-map.md
- [ ] Display success message
- [ ] Close session to save progress

Mark tasks complete as you finish each step.

Step 2: Identify Build

If user specified build (e.g., "archive 01-build-nexus-v3") → Use that

If not → List active builds and ask: "Which build?"

Step 3: Load & Verify

Load 02-builds/active/{ID}-{name}/01-planning/tasks.md and overview.md

Count checkboxes → Calculate progress

Display:

Build: {name}
Progress: X/Y tasks (Z%)
Status: {status}

[If <100%] → "Not complete. Archive anyway? (yes/no)"
[If 100%] → "Ready to archive!"

Step 4: Confirm

Ask: "Archive {name}? This moves it to 02-builds/complete/. (yes/no)"

If "no" → Exit

Step 5: Archive

  1. Move build: 02-builds/active/{ID}-{name}/ → 02-builds/complete/{ID}-{name}/
  2. Update build-map.md:
    • Remove from Active Builds
    • Add to Completed Builds section
    • Clear Current Focus if this was it
  3. Add archive metadata to overview.md:
    archived: 2025-11-02
    
  4. Mark roadmap item complete (REQ-5):
    # Roadmap completion marking (executed inline by AI)
    from pathlib import Path
    from datetime import datetime
    
    roadmap_path = Path("01-memory/roadmap.yaml")
    if roadmap_path.exists():
        import yaml
        with open(roadmap_path) as f:
            roadmap = yaml.safe_load(f)
    
        build_id = "{ID}-{name}"  # The build being archived
    
        for item in roadmap.get("items", []):
            if item.get("build_id") == build_id:
                if not item.get("completed_at"):
                    item["completed_at"] = datetime.now().strftime("%Y-%m-%d")
                    with open(roadmap_path, "w") as f:
                        yaml.dump(roadmap, f, default_flow_style=False, allow_unicode=True)
                    print(f"Marked roadmap item '{item['name']}' as complete")
                break
    

Read the full file on GitHub · 139 lines

Changes

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.

  1. 10d ago First seen · 139 lines · 14 tokens per session scan A c338f9b0c46c

Subscribe to this mod's changes

archive-build is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 843 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens