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 mfwarren/entrepreneur-claude-skills --skill delegation-frameworkgit clone --depth 1 https://github.com/mfwarren/entrepreneur-claude-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/mfwarren/entrepreneur-claude-skills/delegation-framework)<a href="https://agentmods.dev/skills/mfwarren/entrepreneur-claude-skills/delegation-framework"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/delegation-framework/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/mfwarren/entrepreneur-claude-skills/delegation-framework"><img src="https://agentmods.dev/badge/skills/mfwarren/entrepreneur-claude-skills/delegation-framework.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.00003 | $0.00637 |
| Opus 5.5 | $0.00001 | $0.00255 |
| Sonnet 5.5 | $0.00001 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
delegation-framework 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation Framework
Task audit, delegation matrices, and handoff documentation for founders who need to free up their time.
Purpose
Founders often do everything because delegation feels slower than just doing it. This skill audits your tasks, identifies what to delegate, and creates handoff docs so delegation actually works.
Workflow
Step 1: Task Audit
List everything you do in a typical week. For each:
- Time spent
- Enjoyment (love it / neutral / hate it)
- Skill required (only I can do this / anyone could learn this)
- Revenue impact (directly generates revenue / supports revenue / neither)
Step 2: Delegation Matrix
Categorize using the Eisenhower-Delegation hybrid:
| High Skill Required | Low Skill Required | |
|---|---|---|
| High Revenue Impact | Do yourself (core CEO work) | Delegate with oversight |
| Low Revenue Impact | Delegate to specialist | Delegate or eliminate |
Step 3: Delegation Prioritization
Rank by: Time freed x Ease of delegation. Start with tasks that are:
- Time-consuming but low-skill
- Repetitive and documentable
- Not in your zone of genius
Step 4: Handoff Documentation
For each delegated task, create:
- Clear description of the outcome expected
- Step-by-step process (link to SOP if exists)
- Quality standards and examples
- Escalation criteria (when to come back to you)
- Check-in frequency
Step 5: Hiring Recommendation
Based on what's being delegated:
- VA (virtual assistant) for admin/scheduling/data entry
- Freelancer for specialized one-off projects
- Part-time hire for ongoing operational work
- Agency for complex ongoing needs
Output Format
## Delegation Audit: [Your Role]
### Task Inventory
| Task | Hours/Week | Skill | Revenue | Action |
|------|-----------|-------|---------|--------|
| [task] | Xh | Low | Low | Delegate |
### Delegation Priority
1. [Task] — Delegate to [role type]
2. [Task] — Eliminate entirely
### Handoff Doc: [First Task to Delegate]
[Complete handoff documentation]
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 · 90 lines · 3 tokens per session scan A a1315cf6bf92
delegation-framework is a skill published in the GitHub repository mfwarren/entrepreneur-claude-skills (83 stars, last pushed 8mo ago), licensed MIT. It adds 3 tokens to every session and 637 once invoked, about $0.0000 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
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…