Borrowing it
Nothing to install: this file belongs to kivo360/OmoiOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kivo360/OmoiOS/main/.claude/skills/doc-expander/SKILL.mdgit clone --depth 1 https://github.com/kivo360/OmoiOSWrote 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/kivo360/omoios/doc-expander)<a href="https://agentmods.dev/skills/kivo360/omoios/doc-expander"><img src="https://agentmods.dev/badge/skills/kivo360/omoios/doc-expander.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.00066 | $0.01547 |
| Opus 5 | $0.00033 | $0.00773 |
| Sonnet 5 | $0.00013 | $0.00309 |
| Haiku 4.5 | $0.00007 | $0.00155 |
Grade A, and why
doc-expander 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 8d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Expander
Research and expand documentation using DeepWiki and Context7 MCP servers.
Workflow Overview
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ 1. Analyze │────>│ 2. Generate │────>│ 3. Research │
│ Existing Doc │ │ Questions │ │ (DeepWiki/C7) │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ 6. Output │<────│ 5. Structure │<────│ 4. Synthesize │
│ Final Doc │ │ Content │ │ Findings │
└─────────────────┘ └──────────────────┘ └─────────────────┘
Quick Start
Expand Existing Documentation
User: Expand this README with more details about the API
- Read the existing document
- Identify gaps and generate questions
- Research using DeepWiki/Context7
- Synthesize and append findings
Create New Documentation
User: Create comprehensive docs for the fastapi library
- Generate foundational questions
- Research architecture, patterns, examples
- Structure into logical sections
- Output complete documentation
Research Tools
DeepWiki (GitHub Repositories)
Best for: Repository architecture, implementation details, source code patterns
# Get documentation structure
mcp__deepwiki-mcp__read_wiki_structure(repoName="owner/repo")
# Get full documentation
mcp__deepwiki-mcp__read_wiki_contents(repoName="owner/repo")
# Ask specific questions
mcp__deepwiki-mcp__ask_question(
repoName="owner/repo",
question="How does the authentication system work?"
)
When to use DeepWiki:
- Open source libraries on GitHub
- Understanding implementation details
- Finding code examples from source
- Architecture decisions and patterns
Context7 (Library Documentation)
Best for: Official docs, API references, best practices
What ships with it
3 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.
- 8d ago First seen · 252 lines · 66 tokens per session scan A 6d9e3f3e00e7
doc-expander is a skill published in the GitHub repository kivo360/OmoiOS (77 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,547 once invoked, about $0.0003 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
self-awareness
Use when the user asks about Archie itself — what Archie is, how it works, what it can or cannot do, what agents or domains exist, how plugins work, how requests get handled, why something behaves a certain way, what integrations are available, or whether Archie can change itself. Triggers on phrases like "what can…
writing-plugins
Read this before authoring or substantially changing a plugin, agent, or skill for Archie. It's the conceptual playbook for building plugins that fit Archie's multi-agent, single-orchestrator model — what a plugin must respect, why every plugin usually needs an orchestrator-facing skill, and how to think about agents…
triggers
Set up, list, or manage triggers — persistent "do Y when X happens" rules. Use when someone asks Archie to do something on a schedule ("every weekday at 9am…", "every morning post…", "remind the channel weekly…"), to react to new messages in a channel ("whenever someone posts X in.
thread-conduct
Use before posting anywhere outside this task's own thread, or when deciding how much to post inside it. Covers keeping one task in one thread, what to do with a finding that belongs to another team, when a cross-channel post is allowed and how small it must be, how much traffic a thread should carry, and how to…
trigger-task
Use when this task was started by a trigger and you have been given a trigger directory — the one place that survives from one fire of that trigger to the next. Covers reading what an earlier fire left before you start work, what is worth leaving behind so a later fire continues instead of repeating, keeping the…
engineering-pr
Pull request lifecycle management. Use when you need to create a PR, handle PR reviews, resolve merge conflicts, or manage the PR-to-merge workflow. Extends the engineering skill with GitHub-specific tools and decision framework.