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/dasdigitalemomentum/opencode-processing-skills/archive-legacy-docsnpx skills add DasDigitaleMomentum/opencode-processing-skills --skill archive-legacy-docsgit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWrote 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/dasdigitalemomentum/opencode-processing-skills/archive-legacy-docs)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/archive-legacy-docs"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/archive-legacy-docs.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 | $0.00038 | $0.01166 |
| Opus 5 | $0.00019 | $0.00583 |
| Sonnet 5 | $0.00008 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
archive-legacy-docs 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 5d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Archive Legacy Docs
This skill prepares a clean, defined repository state before running generate-docs / create-plan on legacy repositories.
It collects existing documentation artifacts that are scattered/historical, moves them into a single archive directory docs-legacy/, and generates a lightweight index docs-legacy/summary.md.
The archived content is intended to be forensic reference, not canonical documentation.
When to Use
Use this skill when:
- You are onboarding a legacy repo and documentation/plan artifacts are scattered.
- You want
docs/andplans/to start from a clean slate.
Do not use this skill when:
docs/andplans/already follow this framework’s conventions and should be preserved.
Routing Matrix (Who does what)
- Writes:
docs-legacy/**(includingdocs-legacy/summary.md). - Moves: legacy doc files from anywhere in the repo into
docs-legacy/. - Primary: chooses/approves inclusion & exclusion policy (what counts as legacy docs).
- legacy-curator (subagent): performs git-aware moves and writes the summary.
- doc-explorer / implementer: not used.
Execution Model
Key semantics
- git-aware moves:
- If a file is tracked by git, move it with
git mv. - If a file is untracked, move it with filesystem move.
- If a file is tracked by git, move it with
- flat archive:
- All archived files end up directly under
docs-legacy/(no path-preserving). - Name conflicts are resolved by prefixing with the inferred module and adding a stable disambiguator.
- All archived files end up directly under
Module inference (draft)
For each legacy document, infer a "module origin" label (best-effort):
- If path contains a top-level module directory (e.g.
backend/,frontend/,services/<name>/,packages/<name>/), use that. - Else use the first directory segment (
<topdir>). - Else use
root.
Workflow
0) Primary inputs
Primary should provide:
- inclusion patterns (defaults suggested below)
- exclusion patterns (defaults suggested below)
- whether to treat existing
docs/andplans/as legacy (default: yes unless they match this framework)
What ships with it
2 files 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.
- 5d ago First seen · 149 lines · 38 tokens per session scan A cd34b0b14274
archive-legacy-docs is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (58 stars, last pushed 25d ago), licensed MIT. It adds 38 tokens to every session and 1,166 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…