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/parity/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/parity)<a href="https://agentmods.dev/skills/optave/ops-codegraph-tool/parity"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/parity/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/parity"><img src="https://agentmods.dev/badge/skills/optave/ops-codegraph-tool/parity.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 MCP Rug Pull · line 45 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 150 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00029 | $0.02099 |
| Opus 5.5 | $0.00012 | $0.00840 |
| Sonnet 5.5 | $0.00006 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
parity 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/parity — Engine Correctness Parity Audit & Fix
Codegraph has two engines that MUST produce identical results (see CLAUDE.md):
- wasm — JS pipeline + JS extractors + JS edge resolution
- native — full Rust orchestrator (
crates/codegraph-core/src/domain/graph/builder/pipeline.rs) - hybrid — JS pipeline + napi
buildCallEdges(the fallback when the orchestrator is skipped: forced full rebuilds, older addons)
This skill runs scripts/parity-compare.mjs, which builds every
resolution-benchmark fixture with each engine and compares the full node and
edge multisets (kind, name, file, line, confidence, dynamic flag). Any
difference is a bug in the less-accurate engine — never an acceptable gap, and
never something to document as expected. The skill finds the root cause, fixes
it, and re-verifies until the audit is clean.
Arguments
$ARGUMENTSmay contain:--langs a,b,c— restrict to specific fixture names (e.g.javascript,pts-javascript)--hybrid— also audit the hybrid path (recommended; slower)--audit-only— report divergences without fixing them- No arguments — full audit across all fixtures, then fix divergences
Phase 0 — Pre-flight
All steps run from the repo root.
- Confirm
scripts/parity-compare.mjsexists. If not, this repo doesn't have the parity tooling — stop and report. - Build the TypeScript dist (the script imports
dist/index.js, and extractor changes insrc/are invisible until rebuilt):npm run build - Ensure the native addon reflects the local Rust source:
On macOS, locally built binaries must be re-signed or Node kills the process (exit 137):cd crates/codegraph-core && npx napi build --platform --release && cd ../..codesign --sign - --force crates/codegraph-core/*.node - Verify the loader picks up the locally built binary, not the published
package. First check which path is actually resolved:
If the resolved path points tonode -e " const { createRequire } = require('node:module'); const r = createRequire(require.resolve('./dist/index.js')); try { console.log(r.resolve('codegraph-core')); } catch { console.log('not found via require'); } "node_modules/@optave/codegraph-<platform>-<arch>/codegraph-core.node(the installed package), copy your freshly built binary over it:
Then confirm the loader picks it up:cp crates/codegraph-core/*.node node_modules/@optave/codegraph-<platform>-<arch>/codegraph-core.node
Ifnode -e "import('./dist/infrastructure/native.js').then(m => console.log(m.isNativeAvailable()))"false, stop and report — auditing parity without the native engine is meaningless.
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 · 189 lines · 29 tokens per session scan A a5fc8678c724
parity is a skill published in the GitHub repository optave/ops-codegraph-tool (99 stars, last pushed 5d ago), licensed Apache-2.0. It adds 29 tokens to every session and 2,099 once invoked, about $0.0001 per session on Opus 5.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
ix
Answer structural questions about a codebase — what a symbol is, what calls it, what a change breaks, where the hotspots are — from a persistent code graph via the ix CLI, instead of grepping.
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
rust-doctor
Use when Rust code just changed and must not regress, when the user asks to scan, audit or health-check a Cargo workspace, says "rust-doctor", or wants one of its findings explained, tuned or switched off.
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…
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…
verify
Evidence before assertions. Run verification commands and confirm output before claiming work is complete, fixed, or passing. No 'should work now' — run the command, read the output, then claim the result. Covers tests, builds, linting, agent delegation, and requirement checklists.