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-forgenpx skills add optave/ops-codegraph-tool --skill titan-forgegit 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.00036 | $0.04134 |
| Opus 5 | $0.00018 | $0.02067 |
| Sonnet 5 | $0.00007 | $0.00827 |
| Haiku 4.5 | $0.00004 | $0.00413 |
Grade A, and why
titan-forge 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 yesterday.
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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titan FORGE — Execute Sync Plan
You are running the FORGE phase of the Titan Paradigm.
Your goal: read sync.json, find the next incomplete execution phase, make the actual code changes for each target, validate with /titan-gate, commit, and advance state.
Context budget: One phase per invocation. Do not attempt all phases in one session — the context window will fill. Run one phase, report, stop. User re-runs for the next phase.
Arguments (from $ARGUMENTS):
- No args → run next incomplete phase
--phase N→ jump to specific phase--target <name>→ run single target only (for retrying failures)--dry-run→ show what would be done without changing code--yes→ skip confirmation prompt (typically passed by/titan-runorchestrator)
Step 0 — Pre-flight
-
Worktree check:
git rev-parse --show-toplevel && git worktree listIf not in a worktree, stop: "Run
/worktreefirst." -
Sync with main (conditional):
git fetch origin main behind=$(git rev-list HEAD..origin/main --count)-
If
behind == 0→ already up to date, skip the merge entirely and print "Already up to date with origin/main." -
If
behind > 0→ merge:git merge origin/main --no-editIf there are merge conflicts, stop: "Merge conflict detected. Resolve conflicts and re-run
/titan-forge."After a successful merge, run a duplicate-commit check to detect re-applied work:
git log origin/main..HEAD --no-merges --format="%s" | sort | uniq -dIf any subjects are duplicated, print a warning listing them: "WARNING: Duplicate commit subjects found after merge — prior work may have been re-applied. Step 5 will auto-recover completed targets from git log so they are skipped." Do not stop — proceed to Step 3.
-
-
Load artifacts. Read:
.codegraph/titan/sync.json— execution plan (if missing: "Run/titan-syncfirst.").codegraph/titan/titan-state.json— current state.codegraph/titan/gauntlet.ndjson— per-target audit details.codegraph/titan/gauntlet-summary.json— aggregated results
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.
- yesterday First seen · 352 lines · 36 tokens per session scan A 94f7ee2f7c55
titan-forge is a skill published in the GitHub repository optave/ops-codegraph-tool (92 stars, last pushed 3d ago), licensed Apache-2.0. It adds 36 tokens to every session and 4,134 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.
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.