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/commands/webdevtodayjason/titanium-plugins/titanium-plan)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/titanium-plan"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-plan/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/commands/webdevtodayjason/titanium-plugins/titanium-plan"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-plan.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.00007 | $0.02813 |
| Opus 5.5 | $0.00003 | $0.01125 |
| Sonnet 5.5 | $0.00001 | $0.00563 |
| Haiku 4.5 | $0.00001 | $0.00281 |
Grade B, and why
titanium-plan scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 600 ~/.env How it starts
The opening of the file, as written. The whole thing — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titanium Plan Command
You are creating a structured implementation plan from requirements. Follow this systematic process to break down work into actionable tasks with agent assignments.
MCP Tools Used: This command uses the tt MCP server (Titanium Toolkit) which provides:
mcp__plugin_titanium-toolkit_tt__plan_parser- Generates structured implementation plans from requirements
The tt server wraps Python utilities that use Claude AI to analyze requirements and create detailed project plans with task-to-agent assignments.
Agent Assignment: The plan_parser automatically assigns tasks to appropriate specialized agents based on task type (API work → @api-developer, UI work → @frontend-developer, etc.). These assignments are used by /titanium:work to delegate implementation.
Process Overview
This command will:
- Gather and validate requirements
- Use Claude (via
plan_parserMCP tool) to generate structured plan - Validate plan with vibe-check
- Create human-readable documentation
- Store plan in Pieces for future reference
Step 1: Gather Requirements
If user provides a file path:
# User might say: /titanium:plan ~/bmad/output/user-auth-prd.md
- Use Read tool to read the file
- Extract requirements text
If user provides inline description:
# User might say: /titanium:plan
# Then describe: "I need to add JWT authentication with login, register, password reset"
- Write description to
.titanium/requirements.mdusing Write tool - Ask clarifying questions if needed:
- What tech stack? (Node.js, Python, Ruby, etc.)
- What database? (PostgreSQL, MongoDB, etc.)
- Any specific libraries or frameworks?
- Security requirements?
- Performance requirements?
Step 2: Generate Structured Plan
Use the plan_parser MCP tool to generate the plan:
mcp__plugin_titanium-toolkit_tt__plan_parser(
requirements_file: ".titanium/requirements.md",
project_path: "$(pwd)"
)
This will:
- Call Claude with the requirements
- Generate structured JSON plan with:
- Epics (major features)
- Stories (user-facing functionality)
- Tasks (implementation steps)
- Agent assignments
- Time estimates
- Task dependencies
- Save to
.titanium/plan.json - Return the JSON plan directly to Claude
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 · 398 lines · 7 tokens per session scan B 42502c7de656
titanium-plan is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 2,813 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.