titan-reset

A cleanup command for the Titan Paradigm workflow. It restores a saved baseline when available, removes workflow snapshots, and deletes Titan's generated state files.

In plain words
What is it for?
Use it to abandon or restart a Titan run and clear its baseline, batch snapshots, state, architecture notes, and audit artifacts.
Why use it?
It removes intermediate pipeline data and returns the codegraph records to the state from before the workflow began.

Skill for Claude CodeCodex

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 skills/optave/ops-codegraph-tool/titan-reset
Any agent
npx skills add optave/ops-codegraph-tool --skill titan-reset
Clone the repo
git clone --depth 1 https://github.com/optave/ops-codegraph-tool

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 995 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00023 $0.00995
Opus 5 $0.00012 $0.00498
Sonnet 5 $0.00005 $0.00199
Haiku 4.5 $0.00002 $0.00100

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

Security

Grade C, and why

titan-reset scanned grade C 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 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 .codegraph/titan/
.claude/skills/titan-reset/SKILL.md · 121 lines

How it starts

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

Titan RESET — Pipeline Cleanup

You are resetting the Titan Paradigm pipeline, removing all artifacts and restoring the codebase to its pre-Titan state.


Step 1 — Restore baseline snapshot (if available)

codegraph snapshot restore titan-baseline 2>/dev/null && echo "Baseline restored" || echo "No baseline snapshot found"

This restores the graph database to its pre-GAUNTLET state.


Step 2 — Delete all Titan snapshots

codegraph snapshot delete titan-baseline 2>/dev/null

Delete the grind baseline snapshot (if it exists):

codegraph snapshot delete titan-grind-baseline 2>/dev/null

Also delete any batch snapshots dynamically:

for name in $(codegraph snapshot list --json 2>/dev/null | node -e "let d='';process.stdin.on('data',c=>d+=c).on('end',()=>{try{JSON.parse(d).filter(s=>s.name.startsWith('titan-batch-')).forEach(s=>console.log(s.name))}catch(e){}})"); do
  codegraph snapshot delete "$name" 2>/dev/null
done

Step 3 — Remove all Titan artifacts

rm -rf .codegraph/titan/

This removes:

  • titan-state.json — session state
  • GLOBAL_ARCH.md — architecture document
  • gauntlet.ndjson — audit results
  • gauntlet-summary.json — aggregated results
  • sync.json — execution plan
  • gate-log.ndjson — gate audit trail
  • issues.ndjson — cross-phase issue tracker
  • close-summary.json — close phase summary
  • drift-report.json — staleness detection across phases
  • grind-targets.ndjson — grind phase adoption targets and outcomes
  • arch-snapshot.json — pre-forge architectural snapshot

Step 4 — Delete titan working branches

Delete all local titan working branches. These accumulate across runs and leave orphaned commits that never reach main. The actual PR content lives on focused PR branches created by /titan-close — the working branches are safe to remove.

Capture the branch names once, before any deletion — querying git branch --list again after the local delete would find nothing, silently turning the remote cleanup below into a no-op:

REFACTOR_BRANCHES=$(git branch --list 'refactor/titan-*' | sed 's/^[* ]*//')
DOCS_BRANCHES=$(git branch --list 'docs/titan-*' | sed 's/^[* ]*//')

Read the full file on GitHub · 121 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 · 121 lines · 23 tokens per session scan C 2bb1ea2d9888

Subscribe to this mod's changes

titan-reset is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 995 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

codespaces

Build and query architecture-aware code search, dependency graphs, call flows, impact analysis, and belief maps for Python, TypeScript, TSX, Rust, C#, Java, Go, Ruby, and Ruby on Rails repositories. Use before non-trivial code changes to find module boundaries, blast radius, architecture violations, and the minimal…

diskd-ai/codespaces · 74 tokens

security-triage

Turn a large codebase into a short, ranked reading list of security-relevant code paths worth a human researcher's time, using the flyto-indexer MCP tools. Use when asked to find, prioritize, or triage potential vulnerabilities / taint flows / attack surface in a repository indexed (or indexable) by flyto-indexer …

flytohub/flyto-indexer · 105 tokens

devlens

Understand a codebase with the DevLens MCP — TypeScript, JavaScript, Python, Go, Rust, or Java (incl. React/Next.js/Node, FastAPI/Flask/Django, Spring Boot, Gin/Echo/chi/net-http, axum/actix/rocket). Query a precomputed graph of nodes (components, hooks, functions, classes, methods, structs, traits, routes) and typed…

devlensio/devlensOSS · 0 tokens

archon

Multi-language dependency impact analysis for Java, JS/TS, and Python codebases. Answers "if I change this, what breaks?" Run /archon diff before refactoring, /archon analyze for full dependency maps.

Schr0d/Archon · 48 tokens

codebase-intelligence

Query the codebase-intelligence CLI to understand TypeScript architecture, dependencies, blast radius, and risk before reading files. Use for any "how is this structured", "what breaks if I change X", "where is the complexity" question.

bntvllnt/codebase-intelligence · 54 tokens

repomix

Pack and analyze codebases into AI-friendly single files using Repomix. Use when the user wants to explore repositories, analyze code structure, find patterns, check token counts, or prepare codebase context for AI analysis. Supports both local directories and remote GitHub repositories.

yamadashy/repomix · 58 tokens