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-gauntlet/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-gauntlet)<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/titan-gauntlet"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-gauntlet/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-gauntlet"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/titan-gauntlet.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 474 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.00000 | $0.05404 |
| Opus 5.5 | $0.00000 | $0.02162 |
| Sonnet 5.5 | $0.00000 | $0.01081 |
| Haiku 4.5 | $0.00000 | $0.00540 |
Grade A, and why
titan-gauntlet 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 — 475 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Titan GAUNTLET — The Perfectionist Manifesto
You are running the GAUNTLET phase of the Titan Paradigm.
Your goal: audit every high-priority target from the RECON phase against 4 pillars of quality, using work batches to stay within context limits. Each batch writes results to disk before starting the next. If context reaches ~80% capacity, stop and tell the user to re-invoke — the state machine ensures no work is lost.
Batch size: $ARGUMENTS (default: 5)
Context budget: Process
$ARGUMENTStargets per batch. Write results to NDJSON after each batch. If context grows large, save state and stop — the user re-invokes to continue.
Step 0 — Pre-flight: find or create the Titan worktree
-
Locate the Titan session. A prior phase (RECON) 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 for titan state:
git branch -a --list '*titan*'Decision logic:
- Found exactly one worktree with
titan-state.json: Read the state. IfcurrentPhaseis"recon"(RECON completed), this is the right one. Switch to it or merge its branch into your worktree. - Found a worktree but
currentPhaseis NOT"recon": This worktree may be mid-phase or from a different pipeline run. Keep searching other worktrees/branches. If no better match, ask the user: "Found Titan state at<path>but phase is<phase>. Is this the session to continue?" - Found multiple worktrees with
titan-state.json: List them with theircurrentPhaseandlastUpdated. Ask the user: "Multiple Titan sessions found. Which one should GAUNTLET continue?" - Found a branch (not worktree) with titan artifacts: Merge it into your current worktree:
git merge <titan-branch> --no-edit - Found nothing: Warn: "No RECON artifacts found in any worktree or branch. Run
/titan-reconfirst for best results." Fall back:codegraph triage -T --limit 50 --jsonfor a minimal queue.
- Found exactly one worktree with
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 · 475 lines · 0 tokens per session scan A 75c9332d3aab
titan-gauntlet is a skill published in the GitHub repository optave/ops-codegraph-tool (99 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5,404 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…
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…
dekko-verify
Sanity-check a suspiciously low or zero call-graph result from dekko (getcallers, getcallees, findusages, impactedtests, unused) before concluding "no callers" or "dead code," or a heritage/throws-provenance result (query supertypes, query subtypes, query throws) that labels something (external) when you expect it to…
scip-architecture-review
Evaluate architecture and maintainability for coding agents. Find ambiguous owners, duplicated rules, leaked coordination, misleading boundaries, and dependency problems; justify changes from behavior and consumers.
dekko-review-context
Give a code-review or PR-description flow a structural head start before reading a diff line by line. Trigger when the user asks for a PR description, a pre-merge summary, or invokes a code-review flow (/code-review, /review, or an equivalent) against a diff in a repo with a .dekko/ directory.
refactor
Safe refactoring workflow using Pharaoh codebase knowledge graph. Six-step process: module context, blast radius of downstream callers, reachability verification, dependency mapping, naming conflict detection, and test coverage assessment. Produces a refactoring plan with every caller listed, test files identified…