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/claude-plugins/project-awarenessnpx skills add gleanwork/claude-plugins --skill project-awarenessgit 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.00064 | $0.00939 |
| Opus 5 | $0.00032 | $0.00469 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
project-awareness 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 3d 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:
- project-awareness — 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.
Project Awareness
When users ask about projects, their status, or ownership, use Glean to quickly gather relevant context.
Determine the project or topic from the user's request. If no project name is clear, ask the user which project they mean before proceeding.
Tools
This skill drives the standard Glean MCP tools. For full param shape and pitfalls of chat, search, employee_search, and meeting_lookup, see the using-glean reference at using-glean/reference/.
When This Applies
Use this approach when users ask:
- "What's the status of [project]?"
- "Who owns [project]?"
- "What's happening with [project]?"
- "Where does [project] stand?"
- "Who's working on [project]?"
- Quick project context questions
For full handoff documents, suggest the project-handoff skill instead. For questions about the user's own work, suggest the productivity skills.
BE SKEPTICAL
Not all project info is current or reliable. Before presenting information, evaluate:
Currency Test
- Is this information fresh?
- ✅ INCLUDE: Updated in last 2 weeks
- ⚠️ CONTEXT: Last 2-4 weeks (note it's aging)
- ❌ EXCLUDE: Older than 1 month (status likely stale)
Authority Test
- Is this from an official source?
- ✅ INCLUDE: From project lead, official docs, tracking systems
- ⚠️ CONTEXT: From team members (secondary source)
- ❌ EXCLUDE: Informal mentions, dated secondhand reports
Ownership Test
- Is the current owner clear?
- ✅ INCLUDE: Explicitly assigned owner in system
- ⚠️ CONTEXT: Appears to be owner but not confirmed
- ❌ EXCLUDE: Unknown or orphaned projects
Cross-Reference Check
- Do sources agree?
- ✅ INCLUDE: Multiple sources confirm status
- ⚠️ CONTEXT: Single source, note confidence level
- ❌ EXCLUDE: Conflicting information (needs clarification)
Filter Out:
- Projects that appear abandoned (no activity for >3 months)
- Status without context (just "active" is meaningless)
- Owner info you cannot confirm
If unsure: Mark as "Status Unknown - Recommend checking with [owner]"
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.
- 3d ago First seen · 140 lines · 64 tokens per session scan A b671f16a6dee
project-awareness is a skill published in the GitHub repository gleanwork/claude-plugins (25 stars, last pushed 13d ago), licensed MIT. It adds 64 tokens to every session and 939 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…