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 commands/paullukic/coograph/coograph-initgit clone --depth 1 https://github.com/paullukic/coographWrote 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/commands/paullukic/coograph/coograph-init)<a href="https://agentmods.dev/commands/paullukic/coograph/coograph-init"><img src="https://agentmods.dev/badge/commands/paullukic/coograph/coograph-init.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.00842 |
| Opus 5 | $0.00000 | $0.00421 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
coograph-init 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 5d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize a new project with this Coograph template. Interactive setup that auto-detects the tech stack and fills all placeholders.
The full procedure is in .github/skills/coograph-init/SKILL.md. Follow those steps exactly, with these Claude Code-specific substitutions:
| SKILL.md tool | Claude Code equivalent |
|---|---|
vscode_askQuestions |
Ask the user directly in the conversation |
manage_todo_list |
Use task tracking internally |
apply_patch / create_file |
Use Edit / Write tools |
read_file |
Use Read tool |
grep_search |
Use Grep tool |
Steps (summary)
-
Gather info — Ask the user: target project path, which AI tools to set up (Claude Code / VS Code Copilot / both), sections to skip, project-specific rules, whether to enable code-graph, and whether to add global gitignore entries.
-
Detect tech stack — Read the target project's manifest files (package.json, pom.xml, go.mod, Cargo.toml, pyproject.toml, tsconfig.json, etc.) and
src/structure. Extract language, framework, ORM, testing, build tool, linter, commands, and project structure. Present findings and ask the user to confirm before proceeding. -
Copy template files — Copy only what's relevant to the selected tools:
- Claude Code:
CLAUDE.md,.claude/commands/project/(all exceptinitialize.md),.claude/hooks/(all scripts),.claude/settings.json - VS Code Copilot:
.github/agents/,.github/prompts/,AGENTS.md - Always (shared by every tool):
.github/copilot-instructions.md,.github/instructions/,.github/skills/,openspec/config.yaml - Do NOT copy
node_modules/,.omc/, or.claude/settings.local.json - Ask before overwriting any existing file (overwrite / skip / section-by-section)
- Claude Code:
-
Fill placeholders — Replace all
_TBD_and<!-- FILL: ... -->markers using the detected stack info. Delete sections the user said to skip. Add project-specific rules. -
Verify — Grep for remaining
_TBD_or<!-- FILLmarkers. Ask the user for any still missing. Zero markers = done. -
Code-graph setup (if enabled) — See SKILL.md § Step 6 for the full procedure:
- Copy
.github/code-graph/(excludenode_modules/) - Install d3:
cd .github/code-graph && npm install - Ensure
uvis available (install automatically if not) - Add
.code-graph/to.gitignore - Write MCP config(s) for selected tools
- Build initial graph:
uv run --with-requirements .github/code-graph/requirements.txt .github/code-graph/server.py --build - Optionally install git hooks for auto-updates
- Copy
-
Register in projects.json — Add the target project to
projects.jsonin the coograph root (create with{"projects": []}if missing). Entry:{ "path": "<absolute-path>", "tools": [...], "code_graph": true|false, "registered_at": "<date>" }. Then run./setup.shin the coograph root to ensure git hooks are configured for auto-sync on pull.
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.
- 5d ago First seen · 49 lines · 0 tokens per session scan A 2799b3346ecb
coograph-init is a command published in the GitHub repository paullukic/coograph (17 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 842 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 commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.
test-suite
Run comprehensive test suite with coverage analysis.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
help
Explain Ralph Wiggum technique and available commands.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.