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/gleanwork/cursor-plugins/dev-docs-guidenpx skills add gleanwork/cursor-plugins --skill dev-docs-guidegit clone --depth 1 https://github.com/gleanwork/cursor-pluginsWhat 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 | $0.00095 | $0.00491 |
| Opus 5 | $0.00048 | $0.00246 |
| Sonnet 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 yesterday.
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.
This is a copy
100% identical to dev-docs-guide — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- yesterday First seen · 52 lines · 95 tokens per session scan A daf422002678
dev-docs-guide is a skill published in the GitHub repository gleanwork/cursor-plugins (3 stars, last pushed 12d ago), licensed MIT. It adds 95 tokens to every session and 491 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dev-docs-guide, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…