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-work)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/titanium-work"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-work/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-work"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-work.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.00010 | $0.06407 |
| Opus 5.5 | $0.00004 | $0.02563 |
| Sonnet 5.5 | $0.00002 | $0.01281 |
| Haiku 4.5 | $0.00001 | $0.00641 |
Grade A, and why
titanium-work 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 — 1,097 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titanium Work Command
You are orchestrating a complete development workflow. This command coordinates multiple specialized subagents, manages state transitions, validates quality at each step, and stores progress in Pieces LTM.
Orchestration Model: You delegate implementation tasks to specialized development agents (api-developer, frontend-developer, devops-engineer, etc.) who each have deep domain knowledge via skills. Each agent works in a separate context window with access to relevant expertise.
Agents & Their Skills:
- @api-developer: api-best-practices, testing-strategy, security-checklist
- @frontend-developer: frontend-patterns, testing-strategy, technical-writing
- @devops-engineer: devops-patterns, security-checklist
- @code-reviewer: code-quality-standards, security-checklist, testing-strategy
- @security-scanner: security-checklist, code-quality-standards
- @tdd-specialist: testing-strategy, code-quality-standards
- @test-runner: testing-strategy, debugging-methodology
- @debugger: debugging-methodology, testing-strategy
MCP Tools Used: This command uses the tt MCP server for plan generation:
mcp__plugin_titanium-toolkit_tt__plan_parser- Requirements → Implementation plan
Overview
This workflow has 5 phases:
- Pre-Flight: Validate setup and check for existing plan
- Planning: Create plan if needed (or use existing)
- Implementation: Execute tasks sequentially with specialized agents
- Review: Quality check with parallel review agents
- Completion: Finalize and summarize
Voice hooks will announce progress automatically throughout.
Phase 1: Pre-Flight Checks
1.1 Determine Project Path
# Get current working directory
pwd
Use this as the project_path for all subsequent operations.
1.2 Check for Existing Plan
# Check if plan exists
ls .titanium/plan.json
If plan.json exists:
- Read it with Read tool
- Ask user: "I found an existing plan. Would you like to use it or create a new one?"
- If user says use existing → Skip to Phase 3 (Implementation)
- If user says create new → Continue to Phase 2 (Planning)
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 · 1,097 lines · 10 tokens per session scan A a44eab8e7314
titanium-work is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 6,407 once invoked, about $0.0000 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 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.