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 commands/webdevtodayjason/titanium-plugins/titanium-statusgit 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.00006 | $0.02840 |
| Opus 5 | $0.00003 | $0.01420 |
| Sonnet 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 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 — 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.
- 2d 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 7mo ago), licensed MIT. It adds 6 tokens to every session and 2,840 once invoked, about $0.0000 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 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.