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 skills/optave/ops-codegraph-tool/titan-reconnpx skills add optave/ops-codegraph-tool --skill titan-recongit clone --depth 1 https://github.com/optave/ops-codegraph-toolWhat 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.00000 | $0.03081 |
| Opus 5 | $0.00000 | $0.01541 |
| Sonnet 5 | $0.00000 | $0.00616 |
| Haiku 4.5 | $0.00000 | $0.00308 |
Grade A, and why
titan-recon 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titan RECON — Codebase Reconnaissance
You are running the RECON phase of the Titan Paradigm on the target at $ARGUMENTS (default: .).
Your goal: map the dependency graph, identify structural hotspots, name logical domains, produce a global architecture document, propose work batches, and initialize the session state. Everything you produce feeds downstream phases (GAUNTLET, SYNC, GATE) via artifacts in .codegraph/titan/.
Context budget: Every codegraph command MUST use
--jsonto keep output compact. Never dump raw CLI tables into context — parse JSON and extract only what you need.
Step 0 — Pre-flight: worktree and sync
-
Check for worktree isolation:
git rev-parse --show-toplevel && git worktree listIf you are NOT in a worktree, stop: "Run
/worktreefirst. Titan phases write artifacts that should not interfere with other work." -
Sync with main:
git fetch origin main && git merge origin/main --no-editIf there are merge conflicts, stop and ask the user to resolve them.
-
Record the main anchor SHA:
git rev-parse origin/mainStore this as
mainSHAintitan-state.json. All downstream phases use this to detect codebase drift — if main advances between phases, the drift detection mechanism (Step 0.5 in each phase) compares against this anchor to determine what's stale and what needs reassessment.
Step 1 — Build the graph
codegraph build $ARGUMENTS
Record: file count, node count, edge count, engine.
Step 2 — Generate embeddings (for DRY detection in GAUNTLET)
codegraph embed -m minilm
This enables codegraph search for duplicate code detection in downstream phases. If it fails (e.g., missing model), note it and continue — DRY checks will be grep-only.
Verify, don't assume. .codegraph/ is gitignored — graph.db (and its embeddings) is local filesystem state, per worktree. It is never carried over by git merge, a branch switch, or a snapshot restore. Before setting embeddingsAvailable in titan-state.json, smoke-test the current worktree's DB directly:
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 · 362 lines · 0 tokens per session scan A 73d9755cc25d
titan-recon is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,081 tokens. 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
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…
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 …
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…
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.
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.
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.