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/syncgit 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.00017 | $0.00477 |
| Opus 5 | $0.00009 | $0.00238 |
| Sonnet 5 | $0.00003 | $0.00095 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
sync 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.
What it actually says
Sync Branches (standalone utility — not part of the workflow)
PR: $ARGUMENTS (if empty, finds the most recent merged PR)
After you approve and merge a PR into hotfix, run this to propagate changes to the other branches.
Branch flow
hotfix (receives PRs from feature branches)
↓ sync
dev (development branch)
↓ sync
main (stable reference)
↓ sync
release (release branch)
Process
1. Find the merged PR
# If argument given, use it. Otherwise find most recent merged PR to hotfix.
gh pr list --base hotfix --state merged --limit 1
2. Fetch latest
git fetch origin
3. Sync dev to hotfix
git checkout dev
git pull origin dev
git merge origin/hotfix --no-edit
git push origin dev
4. Sync main to dev
git checkout main
git pull origin main
git merge origin/dev --no-edit
git push origin main
5. Sync release to main
git checkout release
git pull origin release
git merge origin/main --no-edit
git push origin release
6. Return to dev
git checkout dev
7. Report
Branches Synced
---------------
┌──────────┬──────────┬─────────────────┐
│ Branch │ SHA │ State │
├──────────┼──────────┼─────────────────┤
│ hotfix │ {sha} │ ← PR merged │
│ dev │ {sha} │ ← synced │
│ main │ {sha} │ ← synced │
│ release │ {sha} │ ← synced │
└──────────┴──────────┴─────────────────┘
Done. All branches contain the latest work.
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 · 89 lines · 17 tokens per session scan A f34ca161b77c
sync is a command published in the GitHub repository cognitx-leyton/codegraph (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 477 once invoked, about $0.0001 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).