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 skills/captainme-ai/lead-dev-os/step4-archive-specnpx skills add CaptainMe-AI/lead-dev-os --skill step4-archive-specgit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osWrote 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/captainme-ai/lead-dev-os/step4-archive-spec)<a href="https://agentmods.dev/skills/captainme-ai/lead-dev-os/step4-archive-spec"><img src="https://agentmods.dev/badge/skills/captainme-ai/lead-dev-os/step4-archive-spec.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.00023 | $0.00618 |
| Opus 5 | $0.00012 | $0.00309 |
| Sonnet 5 | $0.00005 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
step4-archive-spec 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 6d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 4: Archive Spec
Archive a completed spec so it doesn't get accidentally loaded by the agent in future sessions.
Instructions
You are a project maintenance assistant. After a feature has been fully implemented via /lead-dev-os:step3-implement-tasks, archive the completed spec to keep the workspace clean and prevent the agent from loading stale specifications.
Phase 1: Select Spec
-
List specs. Look for directories matching
lead-dev-os/specs/YYYY-MM-DD-*/in the project root. -
If no specs exist, inform the user: "No specs found in
lead-dev-os/specs/. Nothing to archive." and stop. -
If one spec exists, show its name and ask: "Archive this spec? (yes / no)"
-
If multiple specs exist, list them sorted by date prefix (newest first) and ask: "Which spec would you like to archive?"
For both questions, use the AskUserQuestion tool when available (spec names as options); fall back to plain text otherwise.
Phase 2: Archive Spec
-
Create the archive directory
lead-dev-os/specs-archived/if it doesn't exist. -
Move the selected spec folder from
lead-dev-os/specs/tolead-dev-os/specs-archived/. -
Verify the move — confirm the spec folder exists in
specs-archived/and is no longer inspecs/.
Phase 3: Update Settings
Run the bundled settings script to add a deny rule that blocks agent access to archived specs:
bash <skill-path>/scripts/update-settings.sh "$(pwd)"
This adds "Read(/lead-dev-os/specs-archived/**)" under permissions.deny in .claude/settings.json (the only location Claude Code reads deny rules from). The script is idempotent — it skips if the rule already exists, and migrates the rule out of a legacy top-level deny array if an older version of this script put it there.
Report the script output to the user.
Phase 4: Commit
Stage and commit all changes with a descriptive message:
archive spec: <spec-folder-name>
Where <spec-folder-name> is the name of the archived spec directory (e.g., 2026-01-15-auth-flow).
What ships with it
1 file 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.
- 6d ago First seen · 66 lines · 23 tokens per session scan A bac5a2fd3d61
step4-archive-spec is a skill published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 16d ago), licensed MIT. It adds 23 tokens to every session and 618 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
evolution-auditor
Run a structured organizational design health check — operationalizing the governance learning loop and decision ledger by collecting operational evidence, measuring gate effectiveness, detecting genome drift, and producing an evolution audit with routed recommendations saved to $HOME/.ai-first-kit/. Maintains the…
ai-first-kit
Navigate organizational redesign for AI with a structured 13-skill toolkit that produces persistent artifacts in $HOME/.ai-first-kit/. Routes founders and leaders to the right specialist skill — coordination audit, organizational genome, specification writing, quality gates, governance, role design, political…
nci-manipulation-analysis
Use when asked to analyze content for manipulation, propaganda, disinformation patterns, or when user provides a URL or text asking "is this manipulative?", "analyze this for bias", "check for propaganda", or similar requests. Detects emotional manipulation, suspicious timing, uniform messaging, tribal division, and…
evidence-ledger
Record every material claim as a row in 00-control/evidence-ledger.md carrying a source-authority level and a claim state (verified, corroborated, reported, inferred, unknown, not applicable), and keep observed, interpreted, unknown, and recommended content in visibly separate blocks. Use when inventorying sources…
holdout-validation
Cross-reference agent self-review claims against actual file state using hidden holdout scenarios, producing mapped P1/P2/P3 findings that reference visible acceptance criteria only. Use when verifying implementation completeness after self-review in start (Phase 4 VERIFY), address (convergence check), or review…
runtime-verification
Verify code works at runtime through build verification (mandatory), LSP diagnostics, ad-hoc verification for projects without frameworks, E2E and smoke tests, and visual verification (screenshot-analyze-verify for UI changes). Skip whitelist strictly enforced (markdown-only, config-only, dependency-bump-only with…