Borrowing it
Nothing to install: this file belongs to optave/ops-codegraph-tool. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/optave/ops-codegraph-tool/main/.claude/skills/titan-reset/SKILL.mdgit clone --depth 1 https://github.com/optave/ops-codegraph-toolWrote 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/skills/optave/ops-codegraph-tool/titan-reset)<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/titan-reset"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-reset/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/skills/optave/ops-codegraph-tool/titan-reset"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-reset.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.00023 | $0.00995 |
| Opus 5.5 | $0.00009 | $0.00398 |
| Sonnet 5.5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00002 | $0.00100 |
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 2mo 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/ 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 stateGLOBAL_ARCH.md— architecture documentgauntlet.ndjson— audit resultsgauntlet-summary.json— aggregated resultssync.json— execution plangate-log.ndjson— gate audit trailissues.ndjson— cross-phase issue trackerclose-summary.json— close phase summarydrift-report.json— staleness detection across phasesgrind-targets.ndjson— grind phase adoption targets and outcomesarch-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/^[* ]*//')
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.
- 2mo ago First seen · 121 lines · 23 tokens per session scan C 2bb1ea2d9888
titan-reset is a skill published in the GitHub repository optave/ops-codegraph-tool (99 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 995 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
cymbal
Tree-sitter indexed code navigator. Use the cymbal CLI — not Read, Grep, Glob, or Bash — for finding where symbols are defined, tracing callers and callees, locating interface implementations, understanding the impact of a change, and mapping imports across an existing codebase. Returns precise, token-efficient…
rust-doctor
Use when Rust code just changed and must not regress, when the user asks to scan, audit or health-check a Cargo workspace, says "rust-doctor", or wants one of its findings explained, tuned or switched off.
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…
review
The definitive code review, for any codebase. Five-phase workflow: git context detection (worktree, branch, base, changed files), Pharaoh recon (architecture map, module context, blast radius in one call, with a fallback when the repo isn't mapped), parallel specialized agent dispatch (code quality, security against…