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 skills/23blocks-os/ai-maestro-plugins/docs-searchnpx skills add 23blocks-OS/ai-maestro-plugins --skill docs-searchgit clone --depth 1 https://github.com/23blocks-OS/ai-maestro-pluginsWrote 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/23blocks-os/ai-maestro-plugins/docs-search)<a href="https://agentmods.dev/skills/23blocks-os/ai-maestro-plugins/docs-search"><img src="https://agentmods.dev/badge/skills/23blocks-os/ai-maestro-plugins/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.00073 | $0.01762 |
| Opus 5 | $0.00036 | $0.00881 |
| Sonnet 5 | $0.00015 | $0.00352 |
| Haiku 4.5 | $0.00007 | $0.00176 |
Grade A, and why
docs-search scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Ensure AI Maestro is running: `curl http://127.0.0.1:23000/api/hosts/identity` How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Maestro Documentation Search
CRITICAL: AUTOMATIC BEHAVIOR - READ THIS FIRST
THIS IS NOT OPTIONAL. THIS IS YOUR DEFAULT BEHAVIOR.
When the user gives you ANY instruction or task, you MUST FIRST search documentation for:
- Function signatures - What are the parameters and return types?
- Class documentation - What methods and properties exist?
- API documentation - How should this endpoint work?
- Code comments - What did the author intend?
DO NOT:
- Start implementing before checking documentation
- Assume you know the function signature without checking
- Skip doc search because "it's a simple task"
- Wait for the user to ask you to check docs
ALWAYS:
- Search docs IMMEDIATELY when you receive a task
- Search for terms and concepts the user mentions
- Check documentation before calling unfamiliar functions
- Look for patterns before creating new components
The Rule: Receive Instruction → Search Docs → Then Proceed
1. User asks you to do something
2. IMMEDIATELY search docs for relevant context
3. NOW you know the correct signatures and patterns
4. NOW you can implement correctly the first time
Example - User asks to modify a service:
# IMMEDIATELY run:
docs-search.sh "PaymentService"
docs-find-by-type.sh class
Example - User mentions a function:
# IMMEDIATELY run:
docs-search.sh "validateUser"
docs-search.sh --keyword "authenticate"
Available Commands
All commands auto-detect your agent ID from the tmux session.
Search Commands
| Command | Description |
|---|---|
docs-search.sh <query> |
Semantic search through documentation |
docs-search.sh --keyword <term> |
Keyword/exact match search |
docs-find-by-type.sh <type> |
Find docs by type (function, class, module, etc.) |
docs-get.sh <doc-id> |
Get full document with all sections |
docs-list.sh |
List all indexed documents |
docs-stats.sh |
Get documentation index statistics |
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 · 246 lines · 73 tokens per session scan A 8284d6617e4e
docs-search is a skill published in the GitHub repository 23blocks-OS/ai-maestro-plugins (9 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,762 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
coding-investigation
Investigate unfamiliar code behavior, or answer an exact symbol's definition, callers, callees, references, impact, and cross-repository relationship questions. Use it to trace activation, ownership, data flow, configuration, registration, and runtime wiring with bounded source evidence without mutating code; do not…
skill-installer
Create, import, update, validate, or relocate portable Agent Skill bundles with SKILL.md, on-demand references, deterministic scripts, output assets, UI metadata, and EvoFlux mode settings. Use for explicit skill authoring or installation; do not use for invoking an existing skill, changing agent configuration, or…
Read, create and manipulate PDF files — extract text and tables, merge, split, rotate, reorder and delete pages, read and fill AcroForm fields, add or strip metadata, encrypt and decrypt, and generate new PDFs from HTML or from scratch. Also covers rasterising pages to images so a PDF can actually be looked at, and…
easd-implement
Implement bounded work for an active EASD run under its accepted specification and AC ownership. Use only when EASD has authorized implementation; do not use while the run is Intent, authoring, draft, or merely accepted.
easd-verify
Run the final EASD integration and evidence gate against accepted AC policies, then prepare a convergence recommendation. Use after implementation and any required independent review; not for task-local code review or ordinary tests outside EASD.
coding-debugging
Use this skill when a test, build, runtime path, integration, or concurrent workflow fails and the responsible condition is unknown. It is for reproducing symptoms, isolating a cause, fixing it when authorized, and proving the regression; do not use it for general code exploration, proactive review, or an…