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 agentmods add skills/endlessblink/master-plan/tasknpx skills add endlessblink/master-plan --skill taskgit clone --depth 1 https://github.com/endlessblink/master-planWhat 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 | $0.00051 | $0.01055 |
| Opus 5 | $0.00026 | $0.00528 |
| Sonnet 5 | $0.00010 | $0.00211 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
task 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Creator
Quickly add new tasks to MASTER_PLAN.md with automatic sequential ID generation.
Triggers
/master-plan:task- Main command- "add task", "new task", "create task", "track this", "log a bug"
Workflow
Step 1: Find MASTER_PLAN.md
Search for the plan file in order:
docs/MASTER_PLAN.mdMASTER_PLAN.mdmaster-plan.mddocs/master-plan.md
If not found: Create docs/MASTER_PLAN.md using the template structure (see "Initial Setup" section below).
Step 2: Generate Next Task ID
Read the MASTER_PLAN.md file and find all existing task IDs:
- Scan for all occurrences matching
(TASK|BUG|FEATURE|ROAD|IDEA|ISSUE|INQUIRY)-(\d+) - Extract the numeric part from each match
- Find the highest number
- Next ID = highest + 1
CRITICAL: IDs are sequential across ALL types. If TASK-42 and BUG-43 exist, the next ID is 44 regardless of type.
Immediately output to user:
Using task number: [ID]
This must happen BEFORE asking any questions.
Step 3: Gather Task Information
Use AskUserQuestion to collect:
-
Task Type (header: "Type")
TASK— New feature or improvementBUG— Bug fixFEATURE— Major new featureINQUIRY— Investigation (not a fix, just understanding something)
-
Priority (header: "Priority")
P0— Critical / BlockerP1— High priorityP2— Medium priority (Recommended)P3— Low priority / Backlog
Then ask in plain text: "What's the task title? (Keep it concise, under 50 chars)"
Optionally ask: "Any additional description? (Or just press enter to skip)"
Step 4: Add to MASTER_PLAN.md
4a. Add to Roadmap Table (if one exists)
Look for a markdown table with task IDs. Insert a new row:
| **[TYPE]-[ID]** | **[Title]** | **[Priority]** | PLANNED | - |
4b. Add Detailed Section
Add a new ### section at the appropriate place (typically at the end of the active work area, before completed tasks):
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 · 149 lines · 51 tokens per session scan A b0663c486bb4
task is a skill published in the GitHub repository endlessblink/master-plan (27 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,055 once invoked, about $0.0003 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
clinpgx-database
Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.
embedding-strategies
Select and optimize embedding models for semantic search and RAG applications. Use when choosing embedding models, implementing chunking strategies, or optimizing embedding quality for specific domains.
datavis
Comprehensive data visualization toolkit for creating beautiful, mathematically elegant visualizations with D3.js, Chart.js, and custom SVG. Use when (1) building interactive data visualizations, (2) designing color palettes for charts, (3) choosing scales and visual encodings, (4) creating data pipelines from…
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.
vibe-research
Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".
detecting-data-anomalies
Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.