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 gleanwork/claude-plugins --skill dev-docs-guidegit clone --depth 1 https://github.com/gleanwork/claude-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/gleanwork/claude-plugins/dev-docs-guide)<a href="https://agentmods.dev/skills/gleanwork/claude-plugins/dev-docs-guide"><img src="https://agentmods.dev/badge/skills/gleanwork/claude-plugins/dev-docs-guide/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/gleanwork/claude-plugins/dev-docs-guide"><img src="https://agentmods.dev/badge/skills/gleanwork/claude-plugins/dev-docs-guide.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.00491 |
| Opus 5.5 | $0.00038 | $0.00196 |
| Sonnet 5.5 | $0.00019 | $0.00098 |
| Haiku 4.5 | $0.00010 | $0.00049 |
Grade A, and why
dev-docs-guide 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dev-docs-guide — 100% identical, 0 lines differ
What it actually says
Glean Developer Documentation Guide
When users ask about developing with Glean, use the Glean Developer Docs MCP tools.
Tools
This skill uses two tools (refer to them by their bare names):
docs_search— search across the public Glean developer documentationdocs_fetch— get the full content of a documentation page by URL
If these tools aren't visible in the active inventory, the user hasn't configured the Glean Dev Docs MCP server for this host — point them at their host's Glean Dev Docs MCP setup.
When to use
- Glean API — endpoints, authentication, rate limits
- SDK usage — Python, JavaScript installation and examples
- MCP integration — server configuration, tool capabilities
- Platform concepts — indexing, search configuration, connectors
Tool selection
| Need | Tool | Example |
|---|---|---|
| Find relevant docs | docs_search |
docs_search "API authentication" |
| Get implementation details | docs_fetch |
docs_fetch "https://developers.glean.com/docs/api/auth" |
Workflow
- Search first:
docs_search "user query terms" - Review results: identify the most relevant pages
- Fetch for details:
docs_fetch "[url]"for code examples - Cite sources: always include documentation URLs
Query tips
Good: "OAuth token refresh", "Python SDK search API"
Less effective: "authentication", "API", "how to use"
Differentiating from enterprise Glean
This skill is for public developer documentation:
- How to build with Glean APIs / SDKs
- MCP configuration guides
For internal company data (Slack, email, internal docs), use the using-glean skill instead.
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.
- 1mo ago First seen · 52 lines · 95 tokens per session scan A daf422002678
dev-docs-guide is a skill published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 17d ago), licensed MIT. It adds 95 tokens to every session and 491 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…