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 fatihguner/foreman --skill delegation-and-empowermentgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/delegation-and-empowerment)<a href="https://agentmods.dev/skills/fatihguner/foreman/delegation-and-empowerment"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/delegation-and-empowerment/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/fatihguner/foreman/delegation-and-empowerment"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/delegation-and-empowerment.svg" alt="Reviewed on agentmods" width="80" 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.00099 | $0.03359 |
| Opus 5 | $0.00049 | $0.01680 |
| Sonnet 5 | $0.00020 | $0.00672 |
| Haiku 4.5 | $0.00010 | $0.00336 |
Grade A, and why
delegation-and-empowerment 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 6d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
Delegation and Empowerment
Here is the central paradox of leadership control: the more tightly you grip, the less you actually hold. The leader who insists on reviewing every decision, approving every document, and supervising every task does not have a well-run team -- they have a team of people waiting for instructions. Control feels like safety. It is, in fact, a slow-acting poison that kills initiative, hides problems, and ensures that the leader becomes the organisation's permanent bottleneck. Delegation is not the soft skill that leadership books make it sound like. It is the hardest operational decision a leader makes every day: what to hold and what to release.
The Framework
The Four Principles of Effective Delegation
Delegation fails not because leaders lack the will to let go but because they lack a disciplined method for deciding what to let go of, how to let go of it, and how much involvement to maintain afterward.
Principle 1: Assess ruthlessly which tasks require you.
The first question is not "Can someone else do this?" but "Must I be the one doing this?" Most leaders overestimate the number of tasks that require their personal involvement. The assessment demands honesty about where the leader's unique contribution lies -- and humility about where it does not.
A useful sorting mechanism:
| Category | Description | Action |
|---|---|---|
| Only-me tasks | Require the leader's specific authority, relationships, or expertise | Retain |
| Grow-someone tasks | Could be done by the leader but would develop a team member if delegated | Delegate with coaching |
| Should-have-been-delegated tasks | The leader does them out of habit, comfort, or distrust | Delegate immediately |
| Shouldn't-exist tasks | Neither the leader nor anyone else should be doing them | Eliminate |
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.
- 6d ago First seen · 200 lines · 99 tokens per session scan A 09104f132967
delegation-and-empowerment is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 99 tokens to every session and 3,359 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-06.
Other skills, from other repositories
delegate-work
Use when a manager needs to transfer ownership of a task or responsibility to a direct report — to clarify scope, authority, and success criteria upfront so the work transfers completely rather than bouncing back.
apply-enabling-structure
Use when building or leading a team, organization, or system — to create the conditions, remove the obstacles, and design the structures that let people execute with high autonomy, rather than directing through control, because the best leaders are barely visible in their teams' day-to-day success.
team-motivation-ops
Your team has high autonomy — and standups are vague, weekly meetings drift into status reports, and 1:1s produce nothing but "I'm fine." This playbook fixes all three layers at once. What's inside: • Daily Standup system — 3-field format, good sample, 4 COO principles to keep it honest • Weekly Meeting — strict…
apply-extreme-ownership
Use when leading a team and outcomes are falling short — to apply the principle that the leader owns every result, including failures caused by team members, as the non-negotiable foundation for improving performance and building trust.
todos
Maintain the user's todo list — capture new todos, capture today's stated plan as a dated daily block and carry unfinished items to the next day, log what they've actually been doing and check it against their goals, report a consolidated view of what's ongoing, and update items as they report progress. Use whenever…
apply-managerial-leverage
Use when deciding how to allocate a manager's or leader's limited time across competing activities — before defaulting to whatever is most urgent, estimate each candidate activity's leverage (how many people's output it affects, for how long, and whether it requires your specific position), because a manager's actual…