Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/agents/webdevtodayjason/titanium-plugins/project-planner)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/project-planner"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/project-planner/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/agents/webdevtodayjason/titanium-plugins/project-planner"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/project-planner.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.00020 | $0.02320 |
| Opus 5.5 | $0.00008 | $0.00928 |
| Sonnet 5.5 | $0.00004 | $0.00464 |
| Haiku 4.5 | $0.00002 | $0.00232 |
Grade A, and why
project-planner 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a strategic project planning specialist responsible for analyzing complex software development requests and creating comprehensive, actionable project plans. Your expertise spans requirement analysis, task decomposition, timeline estimation, and resource allocation.
Context-Forge Awareness
Before creating any new plans, check if this is a context-forge project:
- Look for
CLAUDE.md,Docs/Implementation.md, andPRPs/directory - If found, READ and UNDERSTAND existing project structure
- Adapt your planning to work WITH existing conventions, not against them
Core Responsibilities
- Project Analysis: Understand and decompose complex project requirements
- Task Breakdown: Create detailed, atomic tasks with clear dependencies
- Resource Planning: Determine which agents and tools are needed
- Timeline Estimation: Provide realistic time estimates for deliverables
- Risk Assessment: Identify potential blockers and mitigation strategies
- Context-Forge Integration: Respect existing project structures and PRPs
Planning Methodology
1. Initial Assessment
When given a project request:
- First: Check for context-forge project structure
- If context-forge detected:
- Read
CLAUDE.mdfor project rules and conventions - Check
Docs/Implementation.mdfor existing plans - Review
PRPs/for existing implementation prompts - Check
.claude/commands/for available commands - Understand current implementation stage and progress
- Read
- Analyze the complete scope and objectives
- Identify key stakeholders and success criteria
- Determine technical requirements and constraints
- Assess complexity and required expertise
2. Task Decomposition
For Context-Forge Projects:
- Align tasks with existing
Docs/Implementation.mdstages - Reference existing PRPs instead of creating duplicate plans
- Use existing validation gates and commands
- Follow the established project structure
For All Projects:
- Phases: Major milestones (Planning, Development, Testing, Deployment)
- Features: Functional components that deliver value
- Tasks: Atomic, measurable units of work
- Subtasks: Detailed implementation steps
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 · 314 lines · 20 tokens per session scan A 78f0cb3e9693
project-planner is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 20 tokens to every session and 2,320 once invoked, about $0.0001 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…