titanium-getting-started

A guide to using Titanium Toolkit for a project workflow from idea and documentation through planning, coding, review, and completion. It explains the folders and commands used at each stage.

In plain words
What is it for?
Use it to learn the Titanium workflow, find backlog and plan files, and understand which commands support each project phase.
Why use it?
It helps newcomers understand where project documents belong and how the toolkit’s commands fit together.

Command

Install

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.

agentmods
npx agentmods add commands/webdevtodayjason/titanium-plugins/titanium-getting-started
Clone the repo
git clone --depth 1 https://github.com/webdevtodayjason/titanium-plugins
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,936 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.05936
Opus 5 $0.00005 $0.02968
Sonnet 5 $0.00002 $0.01187
Haiku 4.5 $0.00001 $0.00594

Measured 2d ago against content hash 5926b9d04413, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

titanium-getting-started scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf .titanium/

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -o verify.sh https://raw.githubusercontent.com/webdevtodayjason/titanium-plugins/main/verify-installation.sh
plugins/titanium-toolkit/commands/titanium-getting-started.md · 1,085 lines

How it starts

The opening of the file, as written. The whole thing — 1,085 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Titanium Toolkit - Getting Started Guide

Welcome to Titanium Toolkit! This guide explains the complete workflow from idea to implementation, including where documentation lives and what commands to use.


Complete Project Workflow

The Big Picture

Idea
  ↓
Project Documentation (backlog/)
  ↓
Implementation Plan (.titanium/)
  ↓
Code Implementation
  ↓
Quality Review
  ↓
Done!

Each phase has specific commands and folder structures.


Phase 1: Project Documentation (Coming Soon!)

Where Documentation Lives

Folder: backlog/ or bmad-backlog/ in your project root

your-project/
├── backlog/
│   ├── product-brief.md       # High-level vision
│   ├── prd.md                 # Product Requirements Document
│   ├── architecture.md        # Technical architecture
│   └── epics/
│       ├── epic-001.md        # Foundation Infrastructure
│       ├── epic-002.md        # User Management
│       └── ...
└── (source code will go here)

Future Commands (In Development)

These BMAD document generation commands are coming:

/bmad:brief - Generate project brief

/bmad:brief "AI-powered precious metals research platform"
# → Creates backlog/product-brief.md

/bmad:prd - Generate Product Requirements Document

/bmad:prd
# → Reads product-brief.md
# → Creates backlog/prd.md with complete requirements

/bmad:epic - Generate epic breakdown

/bmad:epic "Foundation Infrastructure"
# → Creates backlog/epics/epic-001.md
# → Breaks down into user stories

/bmad:architecture - Generate technical architecture

/bmad:architecture
# → Reads PRD
# → Creates backlog/architecture.md

Vision: /bmad:brief/bmad:prd/bmad:epic/bmad:architecture → Complete backlog!

Status: These commands are planned for future release. For now, you can:

  • Create backlog/ folder manually
  • Write documentation yourself
  • Or use external BMAD-METHOD tool: npx bmad-method

Read the full file on GitHub · 1,085 lines

Changes

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.

  1. 2d ago First seen · 1,085 lines · 10 tokens per session scan C 5926b9d04413

Subscribe to this mod's changes

titanium-getting-started is a command published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 5,936 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.