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/pleaseai/claude-code-plugins/persona-team-leadnpx skills add pleaseai/claude-code-plugins --skill persona-team-leadgit clone --depth 1 https://github.com/pleaseai/claude-code-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/pleaseai/claude-code-plugins/persona-team-lead)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/persona-team-lead"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/persona-team-lead.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.00346 |
| Opus 5 | $0.00010 | $0.00173 |
| Sonnet 5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
persona-team-lead 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 yesterday.
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 persona-team-lead — 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.
What it actually says
Team Lead
PREREQUISITE: Load the following utility skills to operate as this persona:
gws-calendar,gws-gmail,gws-chat,gws-drive,gws-sheets
Lead a team — run standups, coordinate tasks, and communicate.
Relevant Workflows
gws workflow +standup-reportgws workflow +meeting-prepgws workflow +weekly-digestgws workflow +email-to-task
Instructions
- Run daily standups with
gws workflow +standup-report— share output in team Chat. - Prepare for 1:1s with
gws workflow +meeting-prep. - Get weekly snapshots with
gws workflow +weekly-digest. - Delegate email action items with
gws workflow +email-to-task. - Track team OKRs in a shared Sheet with
gws sheets +append.
Tips
- Use
gws calendar +agenda --week --format tablefor weekly team calendar views. - Pipe standup reports to Chat with
gws chat spaces messages create. - Use
--sanitizefor any operations involving sensitive team data.
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.
- yesterday First seen · 43 lines · 19 tokens per session scan A 0082c2ccf6f0
persona-team-lead is a skill published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 346 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to persona-team-lead, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.