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 glidermcp/glidermcp.com --skill scout-searchgit clone --depth 1 https://github.com/glidermcp/glidermcp.comWrote 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/glidermcp/glidermcp.com/scout-search)<a href="https://agentmods.dev/skills/glidermcp/glidermcp.com/scout-search"><img src="https://agentmods.dev/badge/skills/glidermcp/glidermcp.com/scout-search/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/glidermcp/glidermcp.com/scout-search"><img src="https://agentmods.dev/badge/skills/glidermcp/glidermcp.com/scout-search.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00448 |
| Opus 5 | $0.00020 | $0.00224 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
scout-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 9d 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.
What it actually says
Scout Code Search Workflow
Use Scout's find as the primary workspace search instead of shell grep, rg, or find. If Glider (C#) or TGlider (TypeScript and JavaScript) is installed, prefer it for its language, and use Scout for every other language and as the universal fallback.
target: auto routes by query shape, and every response echoes the resolved route in data.route. Use strict match modes - literal, regex, or word - when you need exhaustive grep semantics for an audit or a rename survey; fuzzy is ranked top-N with frecency and is never exhaustive. A zero-hit strict search returns an honest empty result rather than silently falling back, so treat it as evidence. Use target: structural for ast-grep patterns ($NAME for one node, $$$ for many), target: symbols for a tree-sitter declaration outline, and target: semantic for natural-language questions. Outside a shipped grammar, or without a semantic model, these degrade to lexical search and say so in meta.degraded - check server_status.tiers before relying on them.
Narrow with path prefixes, include and exclude globs, and language scoping before widening the query, and page through results instead of loosening the match. Results carry workspace-relative paths, 1-based line and column, and trimmed previews, never whole files. Use server_status for index, watcher, and tier health, and sync {full: true} only to force a full rescan, since ordinary queries already flush pending changes.
Scout never mutates workspace source - its only writes are its own state under .glider/scout/ and ~/.glidermcp. When a hit needs semantic follow-up or an edit, hand the file and span to Glider for C#, or TGlider for TypeScript and JavaScript.
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.
- 9d ago First seen · 15 lines · 40 tokens per session scan A bf5094c47666
scout-search is a skill published in the GitHub repository glidermcp/glidermcp.com (16 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 448 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 skills, from other repositories
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time when it should be cached, or when outputs are empty or missing after a…
ax-cpp-agent-observability
Use when writing C++ code with axllm for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ax-go-agent-observability
Use when writing Go code with github.com/ax-llm/ax/packages/go for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ax-java-agent-observability
Use when writing Java code with dev.axllm:ax for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ax-python-agent-observability
Use when writing Python code with axllm for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.