A closing workflow for the Titan Paradigm that reviews branch commits, separates them into focused pull requests, collects tracked issues, and produces a final audit report. A pull request is a proposed set of changes for review before merging.

Use it at the end of a Titan session to locate prior worktrees and branches, split commits, compile the issue tracker, compare final metrics, and generate the report.

It helps turn a large development branch into reviewable pieces and records what was found and measured during the work. A dry-run option lets you inspect the proposed split without creating pull requests or pushing branches.

titan-close — Skill by optave

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-close

Any agent

npx skills add optave/ops-codegraph-tool --skill titan-close

Clone the repo

git clone --depth 1 https://github.com/optave/ops-codegraph-tool

Made for: Claude Code, Codex.

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,623 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 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.

Model	Per session	Once invoked
Fable 5	$0.00032	$0.06623
Opus 5	$0.00016	$0.03312
Sonnet 5	$0.00006	$0.01325
Haiku 4.5	$0.00003	$0.00662

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

Security

Grade A, and why

titan-close 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.

.claude/skills/titan-close/SKILL.md · 682 lines

How it starts

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

Titan CLOSE — PR Splitting & Final Report

You are running the CLOSE phase of the Titan Paradigm.

Your goal: analyze all commits on the current branch, split them into focused PRs for easier review, compile the issue tracker from all phases, capture final metrics, and generate a comprehensive audit report.

Context budget: This phase reads artifacts and git history. Keep codegraph queries targeted — only for final metrics comparison.

Dry-run mode: If $ARGUMENTS contains --dry-run, preview the PR split plan and report without creating PRs or pushing branches.

Step 0 — Pre-flight: find and consolidate the Titan session

Locate the Titan session. All prior phases (RECON → GAUNTLET → SYNC → GATE) may have run across different worktrees or branches. You need to consolidate their work.
```
git worktree list
```
For each worktree, check for Titan artifacts:
```
ls <worktree-path>/.codegraph/titan/titan-state.json 2>/dev/null
```
Also check branches (including remote):
```
git branch -a --list '*titan*'
git branch -a --list '*refactor/*'
```
Decision logic:
- Found exactly one worktree/branch with titan-state.json: Read its currentPhase. If it's "sync" or later, this is the right session. Merge its branch into your worktree.
- Found a worktree but currentPhase is earlier than expected (e.g., "recon" or "gauntlet"): The pipeline may not be complete. Keep searching — there may be a more advanced worktree. If nothing better found, ask the user: "Found Titan state at <path> with phase <phase>. The pipeline appears incomplete. Continue anyway, or should I look elsewhere?"
- Found multiple worktrees with titan-state.json: List them all with currentPhase, lastUpdated, and branch name. The Titan pipeline may have been split across worktrees (RECON in one, GAUNTLET in another). Merge them in phase order into your worktree. If there's ambiguity (e.g., two worktrees at the same phase), ask the user.
- Found branches but no worktrees: Merge the titan branch(es) in phase order: git merge <branch> --no-edit
- Found nothing: Stop: "No Titan session found in any worktree or branch. Run /titan-recon first."

Read the full file on GitHub · 682 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.

2d ago First seen · 682 lines · 32 tokens per session scan A e246fa45d524

Subscribe to this mod's changes

titan-close is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 6,623 once invoked, about $0.0002 per session on Opus 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.

Analytics and metrics Git and workflow Project management ai-agents cli code-analysis dependency-graph impact-analysis incremental-builds

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

titan-close