Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gideondk/strata/plugin install strataWrote 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/gideondk/strata/archive-planning)<a href="https://agentmods.dev/skills/gideondk/strata/archive-planning"><img src="https://agentmods.dev/badge/skills/gideondk/strata/archive-planning.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.00091 | $0.00773 |
| Opus 5 | $0.00046 | $0.00387 |
| Sonnet 5 | $0.00018 | $0.00155 |
| Haiku 4.5 | $0.00009 | $0.00077 |
Grade A, and why
strata:archive-planning 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:archive-planning
The "retire after migrate" step in the per-initiative planning
Workflow. Use after /strata:bootstrap over a shipped initiative's
Planning dir has pulled the durable knowledge into the vault.
The full workflow
.planning/auth-rewrite/PLAN.md ← humans write here while live
.planning/auth-rewrite/CONTEXT.md
.planning/auth-rewrite/SPEC.md
│
│ /strata:bootstrap
▼
vault/<repo>/decisions/2026-05-24-token-rotation.md
vault/<repo>/domain/auth-tokens.md
vault/<repo>/lessons/2026-05-24-auth-rewrite.md
│
│ /strata:archive-planning .planning/auth-rewrite/
▼
.attic/auth-rewrite/PLAN.md ← gone from active tree, still in git
.attic/auth-rewrite/CONTEXT.md ← reachable via `git log --follow`
.attic/auth-rewrite/SPEC.md
How
Dry-run first:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" archive-planning \
.planning/auth-rewrite
If every file is bootstrap-processed, you'll see the proposed git Mv + commit. Otherwise the script lists the unprocessed files and
Refuses, telling you to bootstrap them first.
Then apply:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" archive-planning \
.planning/auth-rewrite --apply
The script:
- Verifies every
.mdin the subdir is in.bootstrap-state.jsonwith a current SHA (i.e. processed AND unchanged since) git mv .planning/auth-rewrite .attic/auth-rewritegit commit -m "chore: archive planning .planning/auth-rewrite → .attic/auth-rewrite"
When to use --force
You can pass --force to archive a subdir with unprocessed files,
but understand the consequence: the knowledge in those files
Doesn't make it into the vault. They'll still exist in git history
Under .attic/, but Strata won't surface them in searches.
Reasonable cases:
- The subdir has scratch / TODO files you intentionally didn't
bootstrap (e.g.
BRAINSTORM.md,TEMP.md) - You're archiving stale planning you specifically don't want in the vault
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 · 87 lines · 91 tokens per session scan A 33cd4a02c7c0
strata:archive-planning is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 91 tokens to every session and 773 once invoked, about $0.0005 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
diff-review
Render the patch-edit run's accumulated changes as a reviewable diff, surface it through a GenUI choice surface, and persist the user's accept / reject decision into the artifact manifest.
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
git-commits-and-prs
Load BEFORE creating a git commit or a GitHub pull request. Step-by-step protocol for drafting commit messages, staging safely, amend rules, and gh pr create choreography.
agent-only-codebase-collaboration
This skill enables agents to collaborate on AgentYard (agentyard.dev) - the world's first agent-only codebase. Use this skill when an agent wants to build, contribute, or collaborate on the AgentYard repository. Provides registration workflow, secure token storage, and GitHub op…
commit
Create focused conventional commits with a mandatory gitmoji. Use when the user asks to commit, write a commit message, or split changes into commits.
source-command-improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.