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/cognitx-leyton/codegraph/implementgit clone --depth 1 https://github.com/cognitx-leyton/codegraphWhat 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.00007 | $0.00614 |
| Opus 5 | $0.00003 | $0.00307 |
| Sonnet 5 | $0.00001 | $0.00123 |
| Haiku 4.5 | $0.00001 | $0.00061 |
Grade A, and why
implement 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Plan (Step 4)
Plan: $ARGUMENTS
Phase 1: Load
Read the plan file and extract:
- Tasks — ordered list of what to implement
- Files to Change — CREATE/UPDATE list
- Patterns to Mirror — code references to follow
- Acceptance Criteria — what "done" looks like
- Validation — how to verify
If plan not found:
Error: Plan not found at $ARGUMENTS
Create one first: /plan_local "feature description"
Phase 2: Verify Starting State
git branch --show-current # must be a feature branch (feat/, fix/, chore/)
git status -s # should be clean
If on a protected branch (main/release/hotfix/dev): STOP, wrong branch. If dirty: warn user, don't proceed until resolved.
Phase 3: Execute
For each task in the plan, in order:
3.1 Read Context
- Read the Mirror / Read first references from the plan
- Understand the pattern before writing code
3.2 Implement
- Make the change as specified in the task
- Follow the mirrored pattern exactly
3.3 Validate Immediately
After EVERY file change:
cd codegraph && python -m compileall codegraph/ -q # syntax check
.venv/bin/python -m pytest tests/ -q # tests
If validation fails:
- Read the error
- Fix the issue
- Re-run validation
- Only proceed to next task when passing
3.4 Track Progress
Use TaskCreate/TaskUpdate to track each task. Mark in_progress when starting, completed when done.
Task 1: UPDATE codegraph/resolver.py ✅
Task 2: CREATE tests/test_new.py ✅
Task 3: UPDATE codegraph/cli.py ⏳ (in progress)
If you deviate from the plan, note what changed and why.
Phase 4: Final Validation
After all tasks complete:
cd codegraph
python -m compileall codegraph/ -q # byte-compile
.venv/bin/python -m pytest tests/ -q # full test suite
.venv/bin/codegraph --help # CLI sanity
All must pass with zero errors.
Phase 5: Report
Implementation Complete
-----------------------
Plan: {plan-path}
Tasks: {N}/{N} completed
Tests: {N} passed, {N} new
Deviations: {none | list}
Ready for: /review-pr
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 · 98 lines · 7 tokens per session scan A 525462ccf912
implement is a command published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 614 once invoked, about $0.0000 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 commands, from other repositories
feedback
Security Design Review — PRD/기획서 기반 보안 의견서·검토 의견서 생성.
compliance
이전 보안 진단 보고서의 Finding들이 패치되었는지 확인하고, 변경된 코드에서 신규 취약점을 탐색합니다.
va
Vulnerability Assessment — 8차원 아키텍처 진단 + Self-Verify + Evidence Verification.
pentest
Penetration Testing — 시나리오 기반 모의해킹 + POC + 라이브 검증 (State Delta 기반).
redteam
Red Team Operations — 인프라 설정 보안 리뷰 + MITRE ATT&CK + Detection Engineering.
verify
Adversarial Verification — 보안 진단 보고서 독립 검증 (Autonomous First).