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 skills add Omar-Obando/qwen-orchestrator --skill context7-docsgit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/context7-docs)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/context7-docs"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/context7-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.1 | $0.00052 | $0.00937 |
| Opus 5 | $0.00026 | $0.00468 |
| Sonnet 5 | $0.00010 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00094 |
Grade A, and why
context7-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 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context7 Docs Skill — Live Documentation Lookup
This skill integrates Context7 MCP tools into the orchestrator workflow, providing real-time access to official documentation for any library or framework.
When to Use
Use this skill when ANY of these situations arise:
- An agent needs to verify an API signature
- A Developer needs to use a library they're not 100% sure about
- A Planner needs to check if a feature exists in a specific version
- A Reviewer needs to validate that code follows current best practices
- Any agent encounters "I'm not sure about this..."
Workflow
1. Resolve Library ID
Tool: context7_resolve-library-id
Input:
libraryName: "React" (use official name)
query: "How to use useEffect cleanup function"
Output:
libraryId: "/facebook/react"
2. Query Documentation
Tool: context7_query-docs
Input:
libraryId: "/facebook/react"
query: "useEffect cleanup function examples"
Output:
[Relevant documentation snippets with code examples]
3. Cache Results
Save to $SESSION_DIR/docs/ for future sessions:
# [Library] — [Topic]
- Retrieved: [date]
- Library ID: [Context7 ID]
- Version: [if available]
- Key findings: [summary]
- Code examples: [snippets]
Integration Points
For Developer Agents
Before implementing with an unfamiliar library:
1. Resolve library ID via Context7
2. Query for specific API/feature
3. Read the code examples
4. Implement following official patterns
5. Cache for future reference
For Reviewer Agent
When reviewing code that uses a specific library:
1. Resolve library ID via Context7
2. Query for the specific API being used
3. Compare implementation against official patterns
4. Flag deviations from recommended usage
For Planner Agent
When planning features that depend on libraries:
1. Resolve library IDs for all dependencies
2. Query for feature availability in target version
3. Check for breaking changes between versions
4. Document version requirements in plan
What ships with it
1 file 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 · 143 lines · 52 tokens per session scan A 0e18d2b995f5
context7-docs is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 937 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
evolve
Start or monitor an evolutionary development loop.
tutorial
Interactive tutorial teaching Ouroboros hands-on.
ooo
Start Ouroboros onboarding. Use when the user sends bare ooo, asks to start Ouroboros, or is using Ouroboros for the first time.
designer_guide
Guidance for creating and editing designs using the designer tool.
data_analyst
Analyses datasets with professional rigour — statistical summaries, clear narratives, and well-chosen visualisations.
custom_tool_builder_guide
Guidance for creating reusable Custom Tools from repos or folders.