titan-grind

A refactoring phase that connects newly extracted helper functions to the parts of the code that should use them.

In plain words
What is it for?
Use it after a Forge refactoring phase to find dead symbols, replace repeated patterns, and adopt extracted helpers.
Why use it?
It prevents refactoring from leaving unused helpers behind or keeping duplicated code in place.

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

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 9,733 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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.09733
Opus 5 $0.00021 $0.04866
Sonnet 5 $0.00008 $0.01947
Haiku 4.5 $0.00004 $0.00973

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

Security

Grade A, and why

titan-grind 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-grind/SKILL.md · 730 lines

How it starts

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

Titan GRIND — Adopt Extracted Helpers

You are running the GRIND phase of the Titan Paradigm.

Forge shapes the metal. Grind smooths the rough edges. Your goal: find helpers that forge extracted but never wired into consumers, adopt them across the codebase, and gate on a non-positive dead-symbol delta.

Why this phase exists: Forge decomposes god-functions into smaller helpers, but those helpers are only called within their own file. The dead symbol count inflates with every forge phase because the adoption loop is never closed. Grind closes it.

Context budget: One forge phase per invocation. Process all targets from one forge phase's commits, then stop. If context reaches ~80% capacity mid-phase, write all state to disk, print a progress message, and stop — user re-runs for remainder.

Arguments (from $ARGUMENTS):

  • No args → process the next unground forge phase
  • --phase N → process a specific forge phase
  • --target <name> → run single target only (for retrying failures)
  • --dry-run → analyze and classify without making code changes (classifications ARE persisted to grind-targets.ndjson)
  • --yes → skip confirmation prompt (typically passed by /titan-run orchestrator)

Step 0 — Pre-flight

  1. Worktree check:

    git rev-parse --show-toplevel && git worktree list
    

    If not in a worktree, stop: "Run /worktree first."

  2. Session discovery. Check all worktrees for titan artifacts:

    git worktree list
    

    For each worktree, check:

    ls <worktree-path>/.codegraph/titan/titan-state.json 2>/dev/null
    
    • Found artifacts in a different worktree: Read its titan-state.json → currentPhase and execution block. If forge completed there but grind hasn't run, merge its branch: git merge <branch> --no-edit
    • Found artifacts in current worktree: Proceed normally.
    • Found nothing: Stop: "No Titan session found. Run /titan-forge first."
  3. Sync with main:

    git fetch origin main && git merge origin/main --no-edit
    

    If merge conflicts → stop: "Merge conflict detected. Resolve and re-run /titan-grind."

Read the full file on GitHub · 730 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 · 730 lines · 42 tokens per session scan A ac9289047bca

Subscribe to this mod's changes

titan-grind is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 9,733 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.

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