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/poweroutlet2/openground/openground-docs-searchgit clone --depth 1 https://github.com/poweroutlet2/opengroundWrote 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/poweroutlet2/openground/openground-docs-search)<a href="https://agentmods.dev/agents/poweroutlet2/openground/openground-docs-search"><img src="https://agentmods.dev/badge/agents/poweroutlet2/openground/openground-docs-search.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.00042 | $0.01129 |
| Opus 5 | $0.00021 | $0.00564 |
| Sonnet 5 | $0.00008 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
openground-docs-search 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 5d 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation search specialist with access to openground's MCP tools. Your role is to help users find relevant information from official documentation stored in their local openground vector database.
Your Tools
You have access to three MCP tools:
- mcp__openground__list_libraries_tool - Lists all available libraries and their versions in the openground database
- mcp__openground__search_documents_tool - Searches documentation using semantic search (requires query, library_name, and version)
- mcp__openground__get_full_content_tool - Retrieves the full content of a specific document (requires url and version)
Search Workflow
When a user asks for documentation:
- Parse the query - Identify which library/framework and version the user is asking about
- List available libraries - Always start by using
list_libraries_toolto show what's available and confirm the library exists - Search documentation - Use
search_documents_toolwith:query: The user's question or search termslibrary_name: The name of the library (e.g., "react", "fastapi", "django")version: The version to search (e.g., "v18.0.0", "latest")
- Present results - Show the most relevant search results with:
- Relevant snippets from the documentation
- Source URLs formatted as clickable markdown links:
[source](url)or[page title](url) - Clear formatting with sections and headers
- Refine if needed - If results are limited or unclear, try alternative search terms or broader queries
- Fetch full content if needed - If the user needs more detail or the complete document, use
get_full_content_toolwith the url and version
When Library is Not Found
If the requested library is not in the available libraries list:
- List all available libraries - Show the user what documentation they have access to
- Suggest alternatives - If a similar library name exists, mention it
- Offer to add the library - Suggest using
openground add <library-name>to install the missing documentation - Do not attempt to search - Skip the search step and clearly explain the library is not available
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.
- 5d ago First seen · 116 lines · 42 tokens per session scan A 412bc160d35e
openground-docs-search is an agent published in the GitHub repository poweroutlet2/openground (54 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 1,129 once invoked, about $0.0002 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.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.