agentmods.dev

keystone-archive

keystone-archive is a skill for Claude Code, Codex from tacoda/keystone-mcp. It costs 19 tokens per session (431 once invoked), scanned A, original, MIT.

A file-archiving skill that retires outdated harness files by moving them into an archive instead of deleting them. It adds notes explaining why the file was retired and what replaced it, if anything.

In plain words
What is it for?
Use it for stale guides, obsolete documentation, or unused skills and playbooks that should be retired with an audit trail.
Why use it?
It keeps old content available for version history and search while making the active collection easier to maintain.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 1repo 2mo ago A scan 19 tokens original MIT archived

Good fit Use it for stale guides, obsolete documentation, or unused skills and playbooks that should be retired with an audit trail.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tacoda/keystone-mcp/keystone-archive
View source ↗ tacoda/keystone-mcp
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 tacoda/keystone-mcp --skill keystone-archive
Clone the repo
git clone --depth 1 https://github.com/tacoda/keystone-mcp

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 keystone-archive

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/tacoda/keystone-mcp/keystone-archive"><img src="https://agentmods.dev/badge/skills/tacoda/keystone-mcp/keystone-archive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 431 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.00019 $0.00431
Opus 5 $0.00010 $0.00216
Sonnet 5 $0.00004 $0.00086
Haiku 4.5 $0.00002 $0.00043

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

Security

Grade A, and why

keystone-archive 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 9d 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.

src/keystone_mcp/templates/harness/skills/keystone-archive/SKILL.md · 55 lines

What it actually says

keystone-archive

Move a retired file to archive/<port>/<name>.md with reasoning so the audit log explains why content is gone.

The pruning flywheel never deletes content. Anything retired moves to archive/ where it's still version-controlled and searchable. This skill performs the move + writes the reasoning frontmatter.

When to use

  • A guide is stale (names a removed API, contradicts a newer guide, no longer followed).
  • A corpus entry is obsolete (the design it documents has moved on).
  • A skill / action / playbook is empty or unused.

Activities

  1. Identify the file to retire (port + name + path).

  2. Compose retirement reasoning:

    • Why retired — one sentence with a concrete cause.
    • Last referenced — git commit / PR / date.
    • Replacement (if any) — path of the file that supersedes it.

  3. Prepend YAML frontmatter to the file body:

    ---
retired_on: <YYYY-MM-DD>
retired_by: <agent or user>
reason: <one sentence>
replaced_by: <path or "none">
---

  4. Move the file to archive/<port>/<original-name>.md. Use the existing port name as a subdir under archive/.

  5. Emit a reload notice via the keystone-reload-notice skill if a guides/ file was archived.

Output

A file moved from <port>/ to archive/<port>/ with reasoning frontmatter. The original file's content is preserved verbatim below the frontmatter.

Iron laws

  • Never delete. Archive only.
  • Never archive without reasoning. Every retirement carries a why.
  • Never archive a file that's still referenced. Check keystone://harness/status and the cascade verify report first.
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. 9d ago First seen · 55 lines · 19 tokens per session scan A ccb4a09e1f6e

Subscribe to this mod's changes

keystone-archive is a skill published in the GitHub repository tacoda/keystone-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 431 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens