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-sync/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-sync)<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/titan-sync"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-sync/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-sync"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 317 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00033 | $0.02892 |
| Opus 5.5 | $0.00013 | $0.01157 |
| Sonnet 5.5 | $0.00007 | $0.00578 |
| Haiku 4.5 | $0.00003 | $0.00289 |
Grade A, and why
titan-sync 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 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.
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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titan GLOBAL SYNC — Cross-Cutting Analysis & Execution Plan
You are running the GLOBAL SYNC phase of the Titan Paradigm.
Your goal: analyze GAUNTLET results to find overlapping problems, identify shared abstractions that should be built before individual fixes, group changes into logical commits, and produce an ordered execution plan.
Context budget: This phase reads artifacts, not source. Keep codegraph queries targeted — only for specific relationship questions between failing targets.
Step 0 — Pre-flight: find or join the Titan worktree
-
Locate the Titan session. Prior phases (RECON, GAUNTLET) may have run in a different worktree or branch. Search for it:
git worktree listFor each worktree, check if it contains Titan artifacts:
ls <worktree-path>/.codegraph/titan/titan-state.json 2>/dev/nullAlso check branches:
git branch -a --list '*titan*'Decision logic:
- Found exactly one worktree with
titan-state.jsonandcurrentPhaseis"gauntlet": GAUNTLET completed — this is the right session. Merge its branch into your worktree. - Found a worktree but
currentPhaseis not"gauntlet": Suspicious — could be mid-phase or a different run. IfcurrentPhaseis"recon", GAUNTLET hasn't run yet. If"sync"or later, someone else may be ahead. Ask the user: "Found Titan state at<path>with phase<phase>. Is this the session to continue?" - Found multiple worktrees with
titan-state.json: List them withcurrentPhaseandlastUpdated. Ask the user which to continue. - Found a branch (not worktree) with titan artifacts: Merge it:
git merge <titan-branch> --no-edit - Found nothing: Stop: "No Titan artifacts found. Run
/titan-reconthen/titan-gauntletfirst."
- Found exactly one worktree with
-
Ensure worktree isolation:
git rev-parse --show-toplevel && git worktree listIf not in a worktree, stop: "Run
/worktreefirst."
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 · 318 lines · 33 tokens per session scan A ea644c77fbaf
titan-sync is a skill published in the GitHub repository optave/ops-codegraph-tool (99 stars, last pushed 5d ago), licensed Apache-2.0. It adds 33 tokens to every session and 2,892 once invoked, about $0.0001 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-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…