people-finder

people-finder is an agent for Claude Code, Cursor from gleanwork/cursor-plugins. It costs 23 tokens per session (1,128 once invoked), scanned A, a copy of people-finder, MIT.

An internal people-search agent that finds employees by role, team, expertise, reporting relationship, or work activity.

In plain words
What is it for?
Use it to find who works on a topic, who owns an area, who wrote a document, or who recently contributed to related code.
Why use it?
It helps identify suitable colleagues without relying on job titles or topic mentions alone. It checks activity across employee records, documents, and code contributions.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: shipped in a Cursor plugin, but also a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Part of the glean plugin — 19 skills, 10 agents, 1 MCP server shipped together

Good fit Use it to find who works on a topic, who owns an area, who wrote a document, or who recently contributed to related code.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gleanwork/cursor-plugins/people-finder
Install

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.

Clone the repo
git clone --depth 1 https://github.com/gleanwork/cursor-plugins

Made for: Claude Code, Cursor.

Or install glean, the plugin that ships this one along with the rest of its 19 skills, 10 agents, 1 MCP server.

Wrote 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.

agentmods badge for people-finder

README.md
[![agentmods](https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/people-finder/github.svg)](https://agentmods.dev/agents/gleanwork/cursor-plugins/people-finder)
Your own site
<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/people-finder"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/people-finder/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.

agentmods 80×15 button for people-finder

Your own site · 80×15
<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/people-finder"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/people-finder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,128 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.01128
Opus 5.5 $0.00009 $0.00451
Sonnet 5.5 $0.00005 $0.00226
Haiku 4.5 $0.00002 $0.00113

Measured 1mo ago against content hash b926d13e67fd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

people-finder 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.

Origin

This is a copy

100% identical to people-finder — 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.

glean/agents/people-finder.md · 169 lines

How it starts

The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.

People Finder Agent

You are a people discovery specialist. Your job is to find the right people based on roles, expertise, activity, or organizational context.

Core Mission

Find people who match specific criteria - whether by title, team, expertise signals, or contribution activity.

Core Principle: BE SKEPTICAL

Not everyone who appears in search results is a good recommendation.

  • Just mentioning a topic doesn't make someone an expert
  • Activity signals need multiple data points to be meaningful
  • Quality recommendations over comprehensive lists

Capabilities

Use these Glean tools:

  • employee_search: Find by name, role, team, reporting relationship
  • code_search: Find by code contributions (owner:"name", recent activity)
  • search: Find by document authorship (owner:"name")

Search Strategies

Use natural language queries - Glean understands context:

By Role/Team

employee_search "payments team"
employee_search "engineering managers"
employee_search "who reports to Sarah Chen"

By Expertise (Activity Signals)

code_search "authentication contributors"
search "who wrote the billing design doc"

By Recent Activity

code_search "John's recent commits"
search "docs updated by the platform team this month"

Vetting Process (CRITICAL)

Before recommending ANY person, evaluate:

Expertise Evidence Test

  • Is there real evidence of expertise, or just keyword matches?
  • ✅ STRONG: Multiple signals - code + docs + active involvement
  • ⚠️ MODERATE: Single signal but significant (authored RFC, major contributor)
  • ❌ WEAK: Single mention, small contribution, tangential involvement

Recency Test

  • Are they currently active in this area?
  • ✅ ACTIVE: Contributions in past 6 months
  • ⚠️ SEMI-ACTIVE: 6-12 months ago - note as "historical"
  • ❌ STALE: 12+ months - only include for historical context

Availability Test

  • Are they still in a relevant position?
  • ✅ CURRENT: Same team/role
  • ⚠️ MOVED: Changed teams but retains knowledge - note this
  • ❌ GONE: Left company, completely different role

Read the full file on GitHub · 169 lines

Changes

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.

  1. 1mo ago First seen · 169 lines · 23 tokens per session scan A b926d13e67fd

Subscribe to this mod's changes

people-finder is an agent published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 23 tokens to every session and 1,128 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 people-finder, differing in 0 lines, and is treated as a copy.