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 plan-prepgit 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/plan-prep)<a href="https://agentmods.dev/skills/gleanwork/claude-plugins/plan-prep"><img src="https://agentmods.dev/badge/skills/gleanwork/claude-plugins/plan-prep/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/plan-prep"><img src="https://agentmods.dev/badge/skills/gleanwork/claude-plugins/plan-prep.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.00031 | $0.01231 |
| Opus 5.5 | $0.00012 | $0.00492 |
| Sonnet 5.5 | $0.00006 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
plan-prep 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:
- plan-prep — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planning Preparation via Glean
Research enterprise context before entering plan mode by gathering design docs, similar implementations, stakeholders, and related systems.
When This Applies
Use plan prep when users:
- Want to research before entering plan mode
- Are planning architectural or strategic changes
- Need to understand related systems before designing
- Want to identify stakeholders and code owners early
- Ask: "plan with glean", "prep for plan", "research before planning"
Why This Matters
Better planning comes from enterprise context:
- Design Decisions: Understand what was tried before, why it worked or didn't
- Similar Implementations: Find proven patterns and learn from past approaches
- Stakeholders: Identify who needs to be involved or has relevant knowledge
- Related Systems: Understand dependencies and integration points
Local tools only see your current repo. This workflow searches your entire organization for existing decisions, patterns, and knowledge.
BE SKEPTICAL
Filter aggressively for relevant, current information.
| Test | ✅ Include | ⚠️ Note | ❌ Exclude |
|---|---|---|---|
| Freshness | <6 months | 6-12 months | 12+ months |
| Relevance | Directly applies | Similar context | Keyword match only |
| Authority | Approved RFCs, official docs | Team wiki, proposals | Rejected/abandoned work |
| Quality | Well-reasoned, proven | Has tradeoffs | Experimental, hacky |
Quality over quantity: 3-4 high-quality findings beat 10 weak ones.
Tool Selection
| Research Need | Glean Tool |
|---|---|
| Find design docs, RFCs, architecture | search |
| Find similar code implementations | code_search |
| Find code owners and stakeholders | code_search + employee_search |
| Find related/dependent systems | code_search |
| Read full document content | read_document |
Workflow
Phase 1: Search for Design & Architecture
Find design documents, RFCs, and architectural decisions related to the task:
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 · 180 lines · 31 tokens per session scan A 581022173b02
plan-prep is a skill published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 17d ago), licensed MIT. It adds 31 tokens to every session and 1,231 once invoked, about $0.0001 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…