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 manager-dot-dev/manager-skills --skill management-transitionsgit clone --depth 1 https://github.com/manager-dot-dev/manager-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/manager-dot-dev/manager-skills/management-transitions)<a href="https://agentmods.dev/skills/manager-dot-dev/manager-skills/management-transitions"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/management-transitions/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/skills/manager-dot-dev/manager-skills/management-transitions"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/management-transitions.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.00143 | $0.03505 |
| Opus 5.5 | $0.00057 | $0.01402 |
| Sonnet 5.5 | $0.00029 | $0.00701 |
| Haiku 4.5 | $0.00014 | $0.00350 |
Grade A, and why
management-transitions 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.
How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Management Transitions
Before Starting
Check for EM context first. If .agents/em-context.md exists, read it.
If .agents/em-context.md does not exist, ask for a minimal manager profile first and save it before giving detailed advice: role/title, team size, team mission or ownership area, and current challenge or priority.
If a specific person is central to the conversation and .agents/reports/[name].md does not exist, ask for a minimal profile for that person first and save it before giving detailed advice: title/level, tenure, strengths, and current challenge or growth area.
If the conversation reveals durable new context later, update .agents/em-context.md or .agents/reports/[name].md automatically. Save stable facts and patterns, not guesses, transient frustration, or unresolved interpretations.
Response Style
Keep the first answer concise and useful. Do not dump the whole framework unless the user asks for depth.
Default to:
- State the likely diagnosis or recommendation first
- Ask at most 2-3 targeted questions only if the missing context changes the advice
- Give the next concrete action and, when useful, exact wording the manager can use
- Mention the relevant framework briefly, but do not explain every part of it
- Offer a deeper version only after the direct answer
How to Use This Skill
- Just became a manager / starting a new role — identify which type → The 4 Types of Transitions
- Taking over a team after an acquisition → Acquisition Integration
- Engineer asking whether to go into management → Counseling Engineers on the Management Track
- First weeks in a new role — what to observe and when to act → The Blue Tape List
- Inherited a struggling or dysfunctional team → Turning Around a Broken Team
- Feeling unfulfilled since switching from IC to manager → The Dopamine Shift
- Second time as a manager and making the same or new mistakes → read
references/extended.md— Second-Time Manager Mistakes - Understanding how the EM role has changed post-2022 → read
references/extended.md— The EM Role in the New Era
What ships with it
2 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.
- 1mo ago First seen · 275 lines · 143 tokens per session scan A effcc1214802
management-transitions is a skill published in the GitHub repository manager-dot-dev/manager-skills (115 stars, last pushed 5mo ago), licensed MIT. It adds 143 tokens to every session and 3,505 once invoked, about $0.0006 per session on Opus 5.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
gsd-milestone-summary
Generate a comprehensive project summary from milestone artifacts for team onboarding and review.
git-pr-workflows-onboard
Plan technical onboarding with environment setup, codebase orientation, team integration, and learning milestones. Use when helping developers join a project or preparing onboarding materials.
team-onboarding-playbook
Design a structured onboarding experience that gets new team members productive in 30, 60, and 90 days. Use when a new hire is joining, when contractors or agency partners need to ramp up, when an existing team is restructuring and members are switching focus, or when current onboarding feels chaotic and slow. Also…
mentor
Draft a teaching-register comment on a GitHub issue or PR thread on the configured repo, aimed at a contributor missing context the maintainer would spell out. Reads the thread, decides whether an intervention is warranted, drafts one comment per the tone guide and convention pointers, and waits for explicit…
product-adoption
Diagnose and design product adoption for onboarding, activation, behavior change, feature discovery, rollout, and sustained use after launch. Covers consumer, B2B, internal-tool, and public-service contexts with evidence-based decision points and cohort segmentation. Does not own acquisition campaigns or marketing…
book-club
A structured workflow for running a book club, covering book selection, scheduling, preparation, discussion, and planning the next meeting.