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/manager-dot-dev/manager-skills/managing-yourselfnpx skills add manager-dot-dev/manager-skills --skill managing-yourselfgit 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/managing-yourself)<a href="https://agentmods.dev/skills/manager-dot-dev/manager-skills/managing-yourself"><img src="https://agentmods.dev/badge/skills/manager-dot-dev/manager-skills/managing-yourself.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.00125 | $0.03283 |
| Opus 5 | $0.00063 | $0.01641 |
| Sonnet 5 | $0.00025 | $0.00657 |
| Haiku 4.5 | $0.00013 | $0.00328 |
Grade A, and why
managing-yourself 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 4d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Yourself
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
Identify the situation first:
- Feeling stuck or wondering if you're doing the EM job right → The 10 Ways EMs Get Stuck (start here)
- Things keep going wrong and you feel like the victim → The Drama Triangle
- Having lots of bad management days → Why Managers Have More Bad Days
- Team seems unmotivated or output is low → Clear the Path
- Made a mistake with someone and need to recover → Repair
- The same problem keeps coming back no matter how you solve it → Problems vs. Polarities
- Your strength as an EM is becoming a failure mode → read
references/extended.md— The Dichotomies - Feeling disconnected from the big picture / product → read
references/extended.md— Balcony Awareness - Facing unexpected criticism, VP grilling, or a major outage → read
references/extended.md— Staying Calm: The BAA Framework - Auditing how your time is split across growth / connection / impact → read
references/extended.md— The EM Grid - Maintaining coding skills or staying hands-on → read
references/extended.md— The Maker/Manager Mode - Getting feedback on management decisions before acting → read
references/extended.md— Code-Reviewing Your Own Decisions - Writing your own performance review → read
references/extended.md— Your Manager Delta - Diagnosing low engagement or bad team culture → read
references/extended.md— The Inversion Model - Auditing your own time allocation → read
references/extended.md— The LNO Framework - Something went wrong and you're figuring out what you missed → read
references/extended.md— Extreme Ownership - Team is scared or anxious during a hard period → read
references/extended.md— The Leader Absorbs Fear - Anything about your manager, managing up, or senior leadership → use
managing-upskill
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.
- 4d ago First seen · 242 lines · 125 tokens per session scan A 5267cc088a6e
managing-yourself is a skill published in the GitHub repository manager-dot-dev/manager-skills (110 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 3,283 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
grid-ctf-ops
Operational knowledge for the gridctf scenario including strategy playbook, lessons learned, and resource references. Use when generating, evaluating, coaching, or debugging gridctf strategies.