What is ensure-repo-graph?

A skill for creating and refreshing local Graphify code graphs for a group of application repositories. A code graph maps relationships in a codebase so later planning can be based on its actual structure.

Use it to resolve repositories from an impact map or project list, sync local copies, build or update deep code graphs, and record each repository's commit and graph fingerprint.

It gives engineering reviews a current, recorded view of candidate repositories and their development branches without changing product-planning approval gates.

ensure-repo-graph — Skill for Claude Code by drivestream-lab

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/drivestream-lab/prayog-skills

agentmods

npx agentmods add skills/drivestream-lab/prayog-skills/ensure-repo-graph

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/ensure-repo-graph/github.svg)](https://agentmods.dev/skills/drivestream-lab/prayog-skills/ensure-repo-graph)

Your own site

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/ensure-repo-graph"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/ensure-repo-graph/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/ensure-repo-graph"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/ensure-repo-graph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00087	$0.01375
Opus 5	$0.00044	$0.00687
Sonnet 5	$0.00017	$0.00275
Haiku 4.5	$0.00009	$0.00137

Measured 12d ago against content hash 33d995b39790, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

ensure-repo-graph 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 12d 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.

skills/engg-reviews/ensure-repo-graph/SKILL.md · 139 lines

How it starts

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

Ensure repo graph

Make in-depth code graphs available for the candidate fleet so /prd-codebase-map can ground the PRD. Do not ask product questions. Do not touch SDD gates.

Provider contract: ../references/codegraph-provider.md.
Handoff: ../references/handoff-adjunct.md.

NON-NEGOTIABLE

This skill is gate-independent. Never create/update/delete impact-map-* or spec-* labels. Never claim Gate 1 readiness.
Use the codegraph provider interface. Phase 1 default: local Graphify CLI.
If Graphify (or configured provider) is missing → outcome blocked with install steps. No PASS and no “light skim” substitute.
Each repo must be on integration branch (default develop) at a recorded SHA before build/update.
Prefer --mode deep for first build; --update when graph exists but SHA changed.
Record per-repo develop_sha + graph_digest (sha256 of graph.json).
No product questions. No PRD edits. No app PRs. No GitHub writes unless the user later authorizes unrelated actions outside this skill.
Dual output: chat fleet table + optional saved status snippet under meta prd/reports/ when useful (Graph-Fleet-Status-{INIT}.md).

Inputs

Initiative id — (REQUIRED) e.g. INIT-001
Candidate repos — (REQUIRED) from one of:
- prd/reports/Impact-Map-{INIT}.md affected (+ optional transitive) list
- PE-supplied list
- resolved config/service-catalog*.yaml hint (only if PE confirms; same one-file resolver as /prd-impact-map — never hardcode a tenant org)
Workspace layout — preferred: {fleet}/pe-workspace/ with fleet.yaml + graphs/{repo}/; app code at ../{repo}; meta at ../drivestream-meta (or {client}-meta). Legacy: cwd = meta with sibling ../{repo} graphs (discouraged — pollutes app trees).
Integration branch — default develop

Process

T0 — Gather

Read the full file on GitHub · 139 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

references/output-template.md 1.2 KB

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.

12d ago First seen · 139 lines · 87 tokens per session scan A 33d995b39790

Subscribe to this mod's changes

ensure-repo-graph is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 87 tokens to every session and 1,375 once invoked, about $0.0004 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-31.

Code review

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

full-repo-review

Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.

notque/vexjoy-agent · 22 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens