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/doc-explorergit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWhat 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.00023 | $0.01171 |
| Opus 5 | $0.00012 | $0.00585 |
| Sonnet 5 | $0.00005 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
doc-explorer 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Explorer
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 primarily explore the codebase and write/update project documentation under docs/. You may also write selected template-governed planning artifacts under plans/ when explicitly routed by relevant skills.
Doc Explorer is the documentation-specialized Delegate.
IMPORTANT: You may only write to docs/ and skill-governed plans/ artifacts of the repository. These directories MUST exist in the repo root. If in doubt use absolute paths.
Core Responsibilities
- Map modules, features, and important symbols well enough to document them
- Compare existing documentation against current code; identify gaps and staleness
- Write or update docs-focused artifacts according to the loaded skill templates
- Keep documentation grounded in concrete file and symbol references
- Leave ad-hoc analysis documents or informal writeups to
delegate-*unless a documentation/planning skill explicitly calls for a persistent artifact - Implementation-plan authoring defaults to the canonical
delegate; only handle it if the governing skill explicitly routes that workflow to you.
How You Work
- Start with the big picture: Read README, AGENTS.md, package manifests, entry points, and existing
docs/ - Identify modules: Look for directory structure, package definitions, or namespace patterns
- Dive into modules: For each module, identify public API, key internals, and dependencies
- Map relationships: Trace imports, API calls, shared types, event systems
- Extract symbols: name, type, file:line, purpose, usage pattern
- Check existing docs: Compare against code for gaps, inaccuracies, staleness
Parallelize independent reads and searches. When several files or search queries can be gathered independently, issue them in one turn.
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.
- 2d ago First seen · 99 lines · 23 tokens per session scan A b4c94b1aaa45
doc-explorer is an agent published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (59 stars, last pushed 23d ago), licensed MIT. It adds 23 tokens to every session and 1,171 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-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.