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 girijashankarj/cursor-handbook --skill task-mastergit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/task-master)<a href="https://agentmods.dev/skills/girijashankarj/cursor-handbook/task-master"><img src="https://agentmods.dev/badge/skills/girijashankarj/cursor-handbook/task-master.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.1 | $0.00033 | $0.00196 |
| Opus 5 | $0.00016 | $0.00098 |
| Sonnet 5 | $0.00007 | $0.00039 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
task-master 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.
What it actually says
Skill: Task master
Trigger
When the user asks to "break this down into tasks," "create a plan," or "what are the steps."
Steps
- Scope — Restate the goal in one sentence.
- List tasks — Output 5–15 ordered tasks (each actionable in 1–2 hours); dependencies first.
- Optional — For each task: owner placeholder, acceptance criteria, or link to doc.
- Summary — One-line summary and suggested order (sequential vs parallel where possible).
Rules
- Tasks should be concrete (e.g. "Add validation in create-order handler" not "Improve API").
- Do not execute the tasks unless the user asks to implement one.
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 · 21 lines · 33 tokens per session scan A 22ffda11d9b4
task-master is a skill published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 196 once invoked, about $0.0002 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-03.
Other skills, from other repositories
housekeep-backlog
Apply-now inventory of parked work — unfinished plans, deferred phases, TODO/FIXME, skipped tests, open findings — into a living BACKLOG.md that diffs new/done/stale. Use when "what's left behind", "inventory TODOs", "consolidate the backlog". Execute → complete-everything. Decisions → docs-adr.
babysit
Keep an already-open PR merge-ready: triage comments, resolve clear conflicts, fix CI. Do not merge. Dirty tree → merge-ready PR → workflow-release-prep. Create/merge PR lifecycle → workflow-pr.
plan-docs-sync
Audit documentation against actual code behavior and plan corrections — no rewrites in this pass. Use when asked to "docs drift", "sync docs with code", "audit documentation", "stale README", "onboarding docs broken", "doc sync plan", "phantom docs", or "docs out of date". Why-we-chose-X / ADRs → docs-adr.
pr-template-builder
Creates GitHub pull request templates, issue templates, and discussion templates with proper YAML configuration. Use when users request "PR template", "issue template", "GitHub templates", "pull request template", or "contribution guidelines".
tech-debt-prioritizer
Scores and prioritizes technical debt by impact, risk, and effort. Provides ranked backlog with ROI analysis and quarterly paydown recommendations. Use for "tech debt", "technical debt management", "code quality", or "refactoring priorities".
dependency-doctor
Audits project dependencies for outdated packages, duplicates, heavy/problematic libraries, security vulnerabilities, and risky version combinations. Generates prioritized reports with security, performance, and maintainability insights, upgrade paths, and safe pinning recommendations. Use when users request…