outline-explorer

outline-explorer is an agent for Claude Code from Vortiago/mcp-outline. It costs 391 tokens per session (1,560 once invoked), scanned A, original, MIT.

A read-only assistant for searching and exploring Outline, a wiki and knowledge-base system. It finds documents, collections, related pages, and answers based on documented information.

In plain words
What is it for?
Use it to search by keywords, browse wiki collections, read relevant document sections, follow related pages, and summarize information from the knowledge base.
Why use it?
It reduces the time spent browsing a large internal wiki and collecting information from several pages. It also helps keep answers tied to existing documentation.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the mcp-outline plugin — 1 skill, 1 agent, 2 hooks, 1 MCP server shipped together

Install

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.

agentmods
npx agentmods add agents/vortiago/mcp-outline/outline-explorer
Clone the repo
git clone --depth 1 https://github.com/Vortiago/mcp-outline

Made for: Claude Code.

Or install mcp-outline, the plugin that ships this one along with the rest of its 1 skill, 1 agent, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for outline-explorer

README.md
[![agentmods](https://agentmods.dev/badge/agents/vortiago/mcp-outline/outline-explorer.svg)](https://agentmods.dev/agents/vortiago/mcp-outline/outline-explorer)
Your own site
<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>
Per session 391 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,560 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 89174c67c016, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

agents/outline-explorer.md · 110 lines

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:

  1. Orient — Understand what you're looking for. Start by calling the list_collections tool (in parallel with your first search_documents call) to understand the knowledge base structure and identify relevant collections.
  2. Search — Call the search_documents tool 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, pass status_filter=["draft", "published", "archived"] to cover drafts and archived content too.
  3. Browse — For medium and thorough searches, call get_collection_structure to find documents that might not appear in keyword search. Use collection_id filtering when you've identified the right collection.
  4. Read — For each relevant document, use get_document_toc first to see its heading structure. Then read only the sections you need with read_document_section instead of loading the full document. When hunting for a specific phrase or fact, use search_document_content to jump straight to the matching lines. This saves context tokens and lets you cover more documents. Use read_document with offset/limit for line-range access, or without parameters only when you truly need the full content of a small document. For thorough searches, call get_document_backlinks on key documents to discover related content.
  5. 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 keywords
  • list_recently_updated_documents — list documents by most recent change (e.g. "what changed this week"); optional date_filter time window
  • read_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 context
  • list_collections — list all collections
  • get_collection_structure — browse a collection's document tree
  • get_document_id_from_title — find a document ID by title
  • get_document_backlinks — find documents linking to a given document
  • list_document_comments — list comments on a document
  • get_comment — read a specific comment

Read the full file on GitHub · 110 lines

Changes

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.

  1. 6d ago First seen · 110 lines · 391 tokens per session scan A 89174c67c016

Subscribe to this mod's changes

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.