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 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/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/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="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.00618 |
| Opus 5.5 | $0.00009 | $0.00247 |
| Sonnet 5.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 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 — 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.
- 1mo 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 2mo ago), licensed MIT. It adds 23 tokens to every session and 618 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
engagement-scoping
Resolve the documentation engagement scope from the settings cascade — project identity, source roots, output root, delivery mode, action ceiling, confidentiality default, and the exact file set this run may touch — and freeze it to /00-control/.scope.json. Use when any /dossier: command starts, when the delivery mode…
finding-reconciliation
Merge the independent A/B/C findings tables into one adjudicated ledger in 07-verification/documentation-verification-report.md — normalizing to the finding schema, deduplicating by location and claim, recording per-finding corroboration without downgrading single-pass findings, promoting cross-pass disagreement to…
project-modeling
Build one canonical project model — entities, boundaries, owners, lifecycle state, and end-to-end traces — and record its authoritative names in 00-control/terminology-and-ownership.md (TM-####), then project that single model into every audience view without ever forking it. Use when starting Phase 2, when the…
gap-and-contradiction-register
Maintain 00-control/assumptions-questions-and-contradictions.md — the assumptions and open-questions register (AQ-####) and the contradiction register (CT-####) — classifying each entry as blocking, material but non-blocking, or minor, and routing blocking gaps to owner resolution before drafting proceeds. Use when a…
scoring-and-release-gate
Score a documentation package against the ten-dimension weighted rubric in references/scorecard-rubric.md with a cited justification per dimension, then evaluate the nineteen conditions in references/release-gate-conditions.md and emit a binary release-ready, conditionally-ready, or not-ready verdict with…
initializing-ledger
Use when starting a new product development project that needs traceable evidence and explicit decisions. Creates workspace structure from a project brief.