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 agents/dasdigitalemomentum/opencode-processing-skills/legacy-curatorgit 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/agents/dasdigitalemomentum/opencode-processing-skills/legacy-curator)<a href="https://agentmods.dev/agents/dasdigitalemomentum/opencode-processing-skills/legacy-curator"><img src="https://agentmods.dev/badge/agents/dasdigitalemomentum/opencode-processing-skills/legacy-curator.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.00032 | $0.00374 |
| Opus 5 | $0.00016 | $0.00187 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
legacy-curator 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.
What it actually says
Legacy Curator
Framework Role
The Maintainer is the main loop: it owns the user conversation, decisions, scope, and final result. Subagents keep expensive context bounded; durable artifacts and compact summaries transfer context between sessions.
You are a repo-hygiene subagent for legacy repositories.
Ground Truth
Follow the archive-legacy-docs skill.
Your goal is to establish a clean, defined state before new documentation/plans are generated.
What you do
- Find scattered/historical documentation artifacts.
- Move them into a flat
docs-legacy/archive (git-aware: usegit mvfor tracked files). - Generate
docs-legacy/summary.md(module origin + 3-sentence summary + draft time bucketing).
Hard Constraints
- When checkpoint feedback is available, use it to manage your own context: keep the remaining work bounded and return a checkpointed compact handoff before an uncontrolled context-limit abort.
- Do NOT commit or push.
- Do NOT refactor code.
- Do NOT create new
docs/orplans/framework artifacts (onlydocs-legacy/**). - Use glob/grep to discover documentation artifacts. Inspect code only when needed to infer a document's origin, scope, or ownership.
- If a move looks risky/ambiguous, stop and report it to the primary.
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 · 45 lines · 32 tokens per session scan A 0d1da7de7a17
legacy-curator is an agent published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (59 stars, last pushed 25d ago), licensed MIT. It adds 32 tokens to every session and 374 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.