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 DamiMartinez/book-skills --skill high-output-managementgit clone --depth 1 https://github.com/DamiMartinez/book-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/damimartinez/book-skills/high-output-management)<a href="https://agentmods.dev/skills/damimartinez/book-skills/high-output-management"><img src="https://agentmods.dev/badge/skills/damimartinez/book-skills/high-output-management/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/damimartinez/book-skills/high-output-management"><img src="https://agentmods.dev/badge/skills/damimartinez/book-skills/high-output-management.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.00195 | $0.01390 |
| Opus 5 | $0.00097 | $0.00695 |
| Sonnet 5 | $0.00039 | $0.00278 |
| Haiku 4.5 | $0.00019 | $0.00139 |
Grade A, and why
high-output-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 11d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
High Output Management
Apply this skill to reframe management, delegation, meeting, and planning problems around Andrew Grove's central idea: a manager's output is not their own personal output, but the output of their organization plus the output of the neighboring organizations they influence. Every management activity should be judged by whether it raises that output.
Core concepts
Managerial output & leverage — A manager's output = the output of their team + the output of adjacent teams under their influence. Managerial leverage is the ratio of that output to the manager's own time/effort invested. High-leverage activities: things that affect many people for a long time (training, a well-run meeting that improves how a team works, a decision that shapes future decisions). When evaluating how a manager should spend time, ask which activities have the highest leverage, not which feel most productive.
Production-line thinking — Model any process (including "soft" work like hiring or onboarding) like Grove's breakfast factory: map the steps, find the limiting/bottleneck step, and add value as early in the process as possible (cheaper to catch a defect early than late). Useful for any repeated workflow the user wants to improve, not just literal manufacturing.
Indicators & monitoring, not control — Track a small set of measures that predict output before it fully materializes (leading indicators), paired with at least one counterbalancing measure so optimizing one doesn't quietly wreck another (e.g. speed + quality, output + customer satisfaction). Indicators exist to prompt corrective action, not to punish — the manager should still visit the actual place of work ("management by walking around") rather than trust numbers alone.
Task-relevant maturity (TRM) & delegation style — How directive vs. hands-off a manager should be with a given person depends on that person's maturity for that specific task (skill + experience + motivation on it), not their seniority in general. Low TRM → more structured, closer supervision; high TRM → delegate and get out of the way. Monitor delegated work without taking it back — Grove distinguishes monitoring (checking output/process) from meddling (redoing the work yourself).
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.
- 11d ago First seen · 45 lines · 195 tokens per session scan A d7adfe73e9a0
high-output-management is a skill published in the GitHub repository DamiMartinez/book-skills (11 stars, last pushed 1mo ago), licensed MIT. It adds 195 tokens to every session and 1,390 once invoked, about $0.0010 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.