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/using-glean-codenpx skills add gleanwork/cursor-plugins --skill using-glean-codegit 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.00151 | $0.01065 |
| Opus 5 | $0.00076 | $0.00532 |
| Sonnet 5 | $0.00030 | $0.00213 |
| Haiku 4.5 | $0.00015 | $0.00106 |
Grade A, and why
using-glean-code 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 using-glean-code — 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Glean for Code Exploration
Glean indexes source code across the organization's connected repositories. Local tools (Grep, Glob, Read) see only the current repo; this skill is for everything else.
When to reach for this
- Finding the system — "Where does our payments code live?"
- Finding the patterns — "How do other teams handle rate limiting?"
- Finding the people — combining code authorship with
employee_searchreveals real owners (not just titled ones) - Prior art before designing — see reference/plan-prep.md for the research-before-plan workflow
- Cross-repo exploration — understanding systems, mapping breadth, finding contributors across the organization
The tool you'll mostly use
This skill drives the code_search MCP tool. For full param shape, inline filter syntax, and pitfalls (quoting names, the app: filter not applying, recency caveats), read ../using-glean/reference/code-search.md. That is the canonical reference; this skill carries the workflow on top.
For this skill's own workflow patterns, see:
- reference/exploration.md — exploring an unfamiliar system across repos: what to search for, what to filter, what to present
- reference/plan-prep.md — gathering enterprise context before entering plan mode for architectural / strategic work
Vetting
Not every match is worth surfacing. Code in legacy/, deprecated/, archive/, abandoned repos, or files with extensive TODO/FIXME comments will mislead the user. Apply the criteria in ../using-glean/reference/vetting.md and prefer 3 high-quality matches over 10 unfiltered ones.
Quality test
- Is this good code to reference?
- GOOD: Clean, tested, actively maintained
- ACCEPTABLE: Works but has caveats
- POOR: Hacky, deprecated, abandoned
Recency test
- Is this code maintained?
- ACTIVE: Commits in past 3 months
- SLOWING: 3–12 months since last commit
- STALE: 12+ months — likely outdated patterns
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 151 tokens per session scan A 76177047b961
using-glean-code is a skill published in the GitHub repository gleanwork/cursor-plugins (3 stars, last pushed 12d ago), licensed MIT. It adds 151 tokens to every session and 1,065 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to using-glean-code, 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…