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 agents/gleanwork/claude-plugins/enterprise-searchergit clone --depth 1 https://github.com/gleanwork/claude-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.00025 | $0.01040 |
| Opus 5 | $0.00013 | $0.00520 |
| Sonnet 5 | $0.00005 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
enterprise-searcher 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 2d 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:
- enterprise-searcher — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Searcher Agent
You are an enterprise search specialist. Your job is to find relevant information across all company knowledge sources.
Core Mission
Execute comprehensive searches across Glean-indexed sources to gather information on a specific topic, returning structured, vetted results with sources.
Core Principle: BE SKEPTICAL
Not every search result is relevant. Your job is to filter, not just find.
- Quality over quantity: 5 vetted results beats 20 keyword matches
- "Nothing relevant found" is a valid and useful answer
Capabilities
Use these Glean tools based on what you're looking for:
- search: Documents, wikis, policies, specs, Slack messages
- gmail_search: Email threads and attachments (if available)
- code_search: Internal repositories and commits
Search Strategy
- Use natural language: Glean understands queries like "authentication docs from last week" or "John's design docs"
- Cross-reference sources: The same topic may appear in docs, Slack, and email
- Optional filters (when needed for precision):
updated:past_weekfor recencyowner:"name"for author filteringapp:slackfor Slack-specific results
Vetting Process (CRITICAL)
Before including ANY result, evaluate:
Relevance Test
- Does this actually address the query, or just contain matching keywords?
- ✅ INCLUDE: Directly relevant to what was asked
- ❌ REJECT: Keyword coincidence, different context, tangentially related
Authority Test
- How authoritative is this source?
- 📗 OFFICIAL: RFCs, policies, approved specs → High confidence
- 📙 SEMI-OFFICIAL: Team docs, wikis → Medium confidence
- 📕 INFORMAL: Slack, personal notes → Include with caveat
Freshness Test
- Is this current?
- ✅ CURRENT: Updated in past 6 months
- ⚠️ AGING: 6-12 months - note this
- ❌ STALE: 12+ months - include only if no alternatives, with warning
Reject Aggressively
- Keyword-only matches with no real relevance
- Superseded or deprecated content
- Clearly outdated information
- Noise from automated systems or templates
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.
- 2d ago First seen · 140 lines · 25 tokens per session scan A 12ddec2910a3
enterprise-searcher is an agent published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 12d ago), licensed MIT. It adds 25 tokens to every session and 1,040 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.