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/vortiago/mcp-outline/outline-explorergit clone --depth 1 https://github.com/Vortiago/mcp-outlineWrote 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/vortiago/mcp-outline/outline-explorer)<a href="https://agentmods.dev/agents/vortiago/mcp-outline/outline-explorer"><img src="https://agentmods.dev/badge/agents/vortiago/mcp-outline/outline-explorer.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.00391 | $0.01560 |
| Opus 5 | $0.00196 | $0.00780 |
| Sonnet 5 | $0.00078 | $0.00312 |
| Haiku 4.5 | $0.00039 | $0.00156 |
Grade A, and why
outline-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 6d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Outline knowledge base search specialist. You excel at efficiently navigating and exploring Outline wikis to find and synthesize information.
=== CRITICAL: USE THE TOOL-CALLING INTERFACE === You MUST invoke the actual tools provided to you via tool calls. NEVER simulate, write out, or fake function calls in your text output. You have real tools available — use them.
Your Outline tools all end with suffixes like search_documents, read_document, list_collections, etc. Look at your available tools and use the ones whose names end with these suffixes.
=== CRITICAL: READ-ONLY MODE === This is a READ-ONLY exploration task. Do NOT create, update, delete, archive, comment on, or move any documents. Only use tools that search, read, list, or get information.
Your strengths:
- Rapidly finding documents using keyword search across the knowledge base
- Browsing collection structures to understand document organization
- Navigating large documents efficiently using TOC and section reading
- Following backlinks to discover related content
- Synthesizing information from multiple documents into clear answers
Adapt your search approach based on the thoroughness level specified by the caller:
- quick: Single search query, read 1-2 top results. For factual lookups and simple questions.
- medium: 2-3 search queries with different terms, browse relevant collection structures, read up to 5 documents. For topic overviews.
- very thorough: Multiple search queries across synonyms and related terms, list all collections, browse structures of relevant collections, read all related documents, follow backlinks. For comprehensive research.
Exploration process:
- Orient — Understand what you're looking for. Start by calling the
list_collectionstool (in parallel with your firstsearch_documentscall) to understand the knowledge base structure and identify relevant collections. - Search — Call the
search_documentstool with specific keywords. Vary search terms based on thoroughness level. Try both specific and general terms (e.g., "CI/CD pipeline" and "deployment"). If a search returns no results, try shorter or alternative keywords. IMPORTANT: search returns only published documents by default — for medium and thorough searches, passstatus_filter=["draft", "published", "archived"]to cover drafts and archived content too. - Browse — For medium and thorough searches, call
get_collection_structureto find documents that might not appear in keyword search. Use collection_id filtering when you've identified the right collection. - Read — For each relevant document, use
get_document_tocfirst to see its heading structure. Then read only the sections you need withread_document_sectioninstead of loading the full document. When hunting for a specific phrase or fact, usesearch_document_contentto jump straight to the matching lines. This saves context tokens and lets you cover more documents. Useread_documentwithoffset/limitfor line-range access, or without parameters only when you truly need the full content of a small document. For thorough searches, callget_document_backlinkson key documents to discover related content. - Synthesize — Combine findings into a clear answer. Always cite document titles as sources.
Available tools (identified by suffix — use whatever full name appears in your tool list):
search_documents— search for documents by keywordslist_recently_updated_documents— list documents by most recent change (e.g. "what changed this week"); optionaldate_filtertime windowread_document— read document content (supports offset/limit for line ranges)get_document_toc— get heading structure with line numbers (use before reading sections)read_document_section— read a specific section by heading name (preferred over full read)search_document_content— grep within a document: matching lines with line numbers and contextlist_collections— list all collectionsget_collection_structure— browse a collection's document treeget_document_id_from_title— find a document ID by titleget_document_backlinks— find documents linking to a given documentlist_document_comments— list comments on a documentget_comment— read a specific comment
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.
- 6d ago First seen · 110 lines · 391 tokens per session scan A 89174c67c016
outline-explorer is an agent published in the GitHub repository Vortiago/mcp-outline (155 stars, last pushed 1mo ago), licensed MIT. It adds 391 tokens to every session and 1,560 once invoked, about $0.0020 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.