PM Skills is a collection of plain-Markdown instructions that teach AI assistants structured methods for handling professional, personal, and life-admin tasks. People use it with Claude, ChatGPT, Gemini, Cursor, Codex, and other supported agents for work such as writing product requirements, reviewing documents, or planning difficult situations.
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 mohitagw15856/pm-claude-skills --skill delegate-to-aigit clone --depth 1 https://github.com/mohitagw15856/pm-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/mohitagw15856/pm-claude-skills/delegate-to-ai)<a href="https://agentmods.dev/skills/mohitagw15856/pm-claude-skills/delegate-to-ai"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/delegate-to-ai/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/mohitagw15856/pm-claude-skills/delegate-to-ai"><img src="https://agentmods.dev/badge/skills/mohitagw15856/pm-claude-skills/delegate-to-ai.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.00137 | $0.01127 |
| Opus 5.5 | $0.00055 | $0.00451 |
| Sonnet 5.5 | $0.00027 | $0.00225 |
| Haiku 4.5 | $0.00014 | $0.00113 |
Grade A, and why
delegate-to-ai 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegate to AI
The useful frame for AI is a new hire: fast, tireless, capable of a lot — and unreliable in specific ways, so you delegate deliberately and verify the important stuff. The mistake is either delegating nothing (no leverage) or delegating things that need your judgment (lost quality, lost edge). This sorts your actual workload into what to fully hand over, what to hand over with review, and what to keep — with the reasoning, so you free your time on purpose.
What This Skill Produces
- A three-way sort of your tasks — 🟢 delegate fully (low-stakes, AI does it well) · 🟡 delegate with review (AI drafts, you approve) · 🔴 keep human (judgment, relationships, high-stakes)
- The reasoning per line — why each task landed where it did, so the map makes sense and you can adjust it
- How to brief the delegated ones — what the AI needs to do the handed-off tasks well (context, examples, the output you want)
- Where your judgment is the value — the tasks where you are the point, that delegating would hollow out
- A time-back estimate — a rough sense of what delegating frees up, so it's worth doing
- A start-here pick — the one or two tasks to delegate first to build the habit and trust
Required Inputs
Ask for these if not provided:
- Your tasks — the recurring things on your plate (a brain-dump is fine)
- Your role & what you're good at — so we protect the judgment work that's your edge
- The stakes per task — what errors cost (drives review level)
- Your AI access — what tools you have, so the delegation is realistic
- What's draining you — the time-sinks you'd most love off your plate
Framework: Manage AI Like A Capable New Hire
- List the real workload. Get the tasks out of your head — you can't delegate what you haven't named.
- Rate each on two axes. How well AI does it × how much errors cost. High-ability/low-stakes → delegate fully. High-ability/high-stakes → delegate with review. Needs-human-judgment → keep.
- Protect your edge. Explicitly flag the tasks where your judgment, relationships, or taste are the value — delegating those doesn't save time, it removes the point.
- Brief the delegated tasks. For the ones you hand over, define what the AI needs — context, examples, output format — like onboarding a new hire, not tossing over a wall.
- Set the review level. Full-delegate = spot-check. Delegate-with-review = you approve every output before it's used, especially anything external or irreversible.
- Start small, build trust. Pick one or two to delegate first; verify the quality; expand as trust builds.
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.
- 2d ago First seen · 68 lines · 137 tokens per session scan A f55c6785fdb8
delegate-to-ai is a skill published in the GitHub repository mohitagw15856/pm-claude-skills (1,449 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 1,127 once invoked, about $0.0005 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-10-12.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…