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 skills add LeadMagic/gtm-skills --skill team-managementgit clone --depth 1 https://github.com/LeadMagic/gtm-skillsWrote 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/leadmagic/gtm-skills/team-management)<a href="https://agentmods.dev/skills/leadmagic/gtm-skills/team-management"><img src="https://agentmods.dev/badge/skills/leadmagic/gtm-skills/team-management.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00095 | $0.01824 |
| Opus 5 | $0.00048 | $0.00912 |
| Sonnet 5 | $0.00019 | $0.00365 |
| Haiku 4.5 | $0.00010 | $0.00182 |
Grade A, and why
team-management 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Management
Overview
Management is a skill, not a promotion. Most founders become managers by default — they hire someone and now they have to manage them. The mistake: treating management as "telling people what to do" instead of building a system that enables autonomous, high-quality work. This skill covers the core management practices every founder needs: 1:1s, feedback, goal-setting, delegation, and scaling yourself as a leader. Based on the operators who built the best-managed companies in tech.
Authoritative Foundations
- Andy Grove — High Output Management (1:1s, task-relevant maturity) — High Output Management (1:1s, task-relevant maturity)
- Kim Scott — Radical Candor (care personally, challenge directly) — Radical Candor (care personally, challenge directly)
- John Doerr — Measure What Matters (OKRs) — Measure What Matters (OKRs)
- Molly Graham — Giving Away Your Legos (delegation) — Giving Away Your Legos (delegation)
- Patty McCord — Powerful (Netflix culture, talent density) — Powerful (Netflix culture, talent density)
- Claire Hughes Johnson — Scaling People (Stripe COO) — Scaling People (Stripe COO)
When to Use
Trigger phrases: "team management", "how to run 1:1s", "performance review template", "how to delegate", "OKR setting", "managing direct reports", "remote team management", "feedback culture", "new manager guide"
Step-by-Step Process
Phase 1: 1:1s (The Foundation of Management)
Cadence: Weekly. 30 minutes. Same day/time every week. Never cancel. If you cancel, you're saying "you're not a priority."
Agenda (owned by the report, not the manager):
- What's going well? (5 min)
- What's challenging / blocking? (10 min — the most important part)
- What do you need from me? (5 min)
- Career / growth discussion (5 min — at least monthly)
- Feedback (5 min — both directions, every time)
Manager's role in 1:1s: Listen 80%. Ask questions. Don't solve problems immediately — ask "what do you think we should do?" first. Take notes. Follow up on action items from last 1:1.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 156 lines · 95 tokens per session scan A 6b22ac7b4b04
team-management is a skill published in the GitHub repository LeadMagic/gtm-skills (48 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 1,824 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
meeting-prep
Build a pre-meeting briefing — who's in the room, what they care about, your goal, and the questions to ask. Trigger when the user asks to prep for a meeting or call, "what should I know before", or names an upcoming meeting.
calendar-followup
Surface unfinished follow-ups from last week's external meetings. Trigger when the user asks "who do I need to follow up with", "what meetings haven't I followed up on", or as part of the morning briefing ritual.
onboarding-handoff
Run the Won→onboarding handoff — the seam most teams drop. Trigger when a deal is marked won/closed-won, when the user says "we won X", "hand this off to onboarding", "kick off the new customer", or "onboarding checklist".
product-signal
Route post-sale and field signals into product's roadmap queue, and write the buyer-facing line for anything shipped. Trigger when the user says "what should product hear", "triage the roadmap signals", "route this to product", "feature request", or "what does this feature mean for the buyer".
follow-up
Debrief a meeting and draft the follow-up. Trigger when the user asks to debrief a call, follow up, or "what do I send after that meeting".
triage
Triage a list of incoming items into do-now / schedule / delegate / drop. Trigger when the user pastes a list and asks to triage, prioritize, or "what should I do first".