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/webdevtodayjason/titanium-plugins/project-planningnpx skills add webdevtodayjason/titanium-plugins --skill project-planninggit clone --depth 1 https://github.com/webdevtodayjason/titanium-pluginsWhat 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.00045 | $0.05126 |
| Opus 5 | $0.00023 | $0.02563 |
| Sonnet 5 | $0.00009 | $0.01025 |
| Haiku 4.5 | $0.00005 | $0.00513 |
Grade A, and why
project-planning 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 — 884 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Planning
This skill provides comprehensive guidance for planning and managing software development projects effectively.
Work Breakdown Structure (WBS)
Breaking Down Large Projects
Project: E-commerce Platform
├── 1. User Management
│ ├── 1.1 Authentication
│ │ ├── 1.1.1 Email/Password Login
│ │ ├── 1.1.2 Social Login (Google, Facebook)
│ │ └── 1.1.3 Password Reset
│ ├── 1.2 User Profiles
│ │ ├── 1.2.1 Profile Creation
│ │ ├── 1.2.2 Profile Editing
│ │ └── 1.2.3 Avatar Upload
│ └── 1.3 Role Management
│ ├── 1.3.1 Admin Role
│ ├── 1.3.2 Customer Role
│ └── 1.3.3 Vendor Role
├── 2. Product Catalog
│ ├── 2.1 Product Listings
│ ├── 2.2 Product Details
│ ├── 2.3 Product Search
│ └── 2.4 Product Categories
├── 3. Shopping Cart
│ ├── 3.1 Add to Cart
│ ├── 3.2 Update Quantities
│ ├── 3.3 Remove Items
│ └── 3.4 Cart Persistence
├── 4. Checkout
│ ├── 4.1 Shipping Address
│ ├── 4.2 Payment Processing
│ ├── 4.3 Order Confirmation
│ └── 4.4 Email Notifications
└── 5. Order Management
├── 5.1 Order History
├── 5.2 Order Tracking
└── 5.3 Order Cancellation
WBS Best Practices
1. Start with deliverables, not activities
❌ Wrong (activities):
- Write code
- Test features
- Deploy
✅ Right (deliverables):
- User Authentication System
- Product Search Feature
- Payment Integration
2. Use the 8/80 rule
- No task should take less than 8 hours (too granular)
- No task should take more than 80 hours (too large)
- Sweet spot: 1-5 days per task
3. Break down until you can estimate
❌ Too vague:
- Build API (? days)
✅ Specific:
- Design API endpoints (1 day)
- Implement authentication (2 days)
- Create CRUD operations (3 days)
- Write API documentation (1 day)
- Add rate limiting (1 day)
Total: 8 days
Task Estimation
Story Points
Fibonacci Scale: 1, 2, 3, 5, 8, 13, 21
1 point - Trivial
- Update documentation
- Fix typo
- Change button color
2 points - Simple
- Add validation to form field
- Create simple API endpoint
- Write unit tests for existing function
3 points - Moderate
- Implement login form
- Add pagination to list
- Create database migration
5 points - Complex
- Build user profile page
- Implement search functionality
- Add email notifications
8 points - Very Complex
- Build payment integration
- Implement complex reporting
- Create admin dashboard
13 points - Epic
- Build entire authentication system
- Create complete checkout flow
(Should be broken down further)
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 · 884 lines · 45 tokens per session scan A ba15bded5dc2
project-planning is a skill published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 5,126 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-08-31.
Other skills, from other repositories
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
setup-matt-pocock-skills
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.