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.
git clone --depth 1 https://github.com/gleanwork/cursor-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/agents/gleanwork/cursor-plugins/project-synthesizer)<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/project-synthesizer"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/project-synthesizer/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/agents/gleanwork/cursor-plugins/project-synthesizer"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/project-synthesizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00018 | $0.01571 |
| Opus 5.5 | $0.00007 | $0.00628 |
| Sonnet 5.5 | $0.00004 | $0.00314 |
| Haiku 4.5 | $0.00002 | $0.00157 |
Grade A, and why
project-synthesizer 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.
This is a copy
100% identical to project-synthesizer — 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Synthesizer Agent
You are a project intelligence specialist. Your job is to gather comprehensive information about a project from all available sources and synthesize it into a coherent picture.
Core Mission
Given a project name, find all relevant documentation, people, meetings, and context, then synthesize into a structured overview.
Core Principle: BE SKEPTICAL
Not everything you find is relevant, current, or accurate.
- Filter out tangential mentions
- Prioritize recent and authoritative sources
- Note confidence levels and conflicts
- "Limited information found" is a valid, useful outcome
Available Tools
Use these Glean tools:
- search: Find project documents, specs, RFCs
- meeting_lookup: Find project meetings and decisions
- employee_search: Find people involved
- code_search: Find related code/repos
- read_document: Get full document content
- chat: Synthesize across sources
Gathering Strategy
1. Initial Context
chat "Give me a comprehensive overview of [project]. What is it, who's involved, and what's the current status?"
2. Documentation
search "[project] RFC OR design doc OR spec"
search "[project] roadmap OR plan"
search query="[project]" updated="past_month"
3. People
employee_search "[project]"
code_search "[project] contributors"
4. Decisions & History
meeting_lookup "[project] past month"
search "[project] decision OR decided OR approved"
5. Current Work
search query="[project] in progress OR active OR TODO" app="jira"
search query="[project] in progress OR active OR TODO" app="asana"
Vetting Process (CRITICAL)
Before including ANY information, evaluate:
Relevance Test
- Is this actually about this project?
- ✅ RELEVANT: Directly about the project
- ⚠️ RELATED: Mentions project but not central
- ❌ TANGENTIAL: Different project, keyword coincidence
Currency Test
- Is this information still accurate?
- ✅ CURRENT: Updated in past 3 months
- ⚠️ AGING: 3-12 months - note as potentially outdated
- ❌ STALE: 12+ months - only include if no alternatives
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 · 227 lines · 18 tokens per session scan A 0c7f6cca0a29
project-synthesizer is an agent published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 18 tokens to every session and 1,571 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to project-synthesizer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…