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-status)<a href="https://agentmods.dev/commands/webdevtodayjason/titanium-plugins/titanium-status"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-status/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-status"><img src="https://agentmods.dev/badge/commands/webdevtodayjason/titanium-plugins/titanium-status.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.00006 | $0.02840 |
| Opus 5.5 | $0.00002 | $0.01136 |
| Sonnet 5.5 | $0.00001 | $0.00568 |
| Haiku 4.5 | $0.00001 | $0.00284 |
Grade A, and why
titanium-status 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 — 556 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titanium Status Command
You are reporting on the current workflow state and progress. This command provides a comprehensive view of where the project stands, what's been completed, and what's remaining.
Overview
This command will:
- Check for active workflow state
- Query Pieces for recent work
- Analyze TodoWrite progress (if available)
- Check for existing plan
- Calculate progress metrics
- Present formatted status report
- Optionally provide voice summary
Step 1: Check for Active Workflow
Check Workflow State File
uv run ${CLAUDE_PLUGIN_ROOT}/hooks/utils/workflow/workflow_state.py get "$(pwd)"
If workflow exists:
- Parse the JSON response
- Extract:
- workflow_type
- goal
- status (planning/in_progress/completed/failed)
- current_phase
- started_at timestamp
- phases history
If no workflow exists:
- Report: "No active workflow found in this project"
- Check for plan anyway (might be planning only)
- Query Pieces for any previous work
Step 2: Query Pieces for Context
Use Pieces LTM to get recent work history:
mcp__Pieces__ask_pieces_ltm(
question: "What work has been done in the last session on this project at [current directory]? What was being worked on? What was completed? What was left unfinished?",
chat_llm: "claude-sonnet-4-5",
topics: ["workflow", "implementation", "development"],
application_sources: ["Code"]
)
Extract from Pieces:
- Recent activities
- What was completed
- What's in progress
- Any issues encountered
- Last known state
Step 3: Check for Plan
# Check if plan exists
ls .titanium/plan.json
If plan exists:
- Read
.titanium/plan.json - Extract:
- Total epics count
- Total stories count
- Total tasks count
- Estimated total time
- List of agents needed
Calculate progress (if TodoWrite is available):
- Count completed tasks vs total tasks
- Calculate percentage complete
- Identify current task (first pending task)
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 · 556 lines · 6 tokens per session scan A a428a3526e08
titanium-status is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 6 tokens to every session and 2,840 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
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.