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 skills/tae2089/code-context-graph/ccg-analyzenpx skills add tae2089/code-context-graph --skill ccg-analyzegit clone --depth 1 https://github.com/tae2089/code-context-graphWhat 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.00087 | $0.00179 |
| Opus 5 | $0.00044 | $0.00089 |
| Sonnet 5 | $0.00017 | $0.00036 |
| Haiku 4.5 | $0.00009 | $0.00018 |
Grade A, and why
ccg-analyze 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 3d 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.
What it actually says
CCG Analyze Runtime Adapter
Proceed only when the user explicitly names ccg-analyze in the current
request. Read the canonical CCG analyze skill
completely before acting. Resolve its linked resources relative to the canonical
skill directory and follow its analysis boundary and completion instructions
for the current task.
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.
- 3d ago First seen · 14 lines · 87 tokens per session scan A 94d63af15c6d
ccg-analyze is a skill published in the GitHub repository tae2089/code-context-graph (17 stars, last pushed 11d ago), licensed MIT. It adds 87 tokens to every session and 179 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-30.
Other skills, from other repositories
nopua
The anti-PUA. Drives AI with wisdom, trust, and inner motivation instead of fear and threats. Activates on: task failed 2+ times, about to give up, suggesting user do it manually, blaming environment unverified, stuck in loops, passive behavior, or user frustration ('try harder', 'figure it out', '换个方法', '为什么还不行').…
roadmap
Read the feature roadmap, find the next unplanned phase, brainstorm it, and update the roadmap with the resulting document name.
paad-help
Use when the user asks which paad skills exist, what a paad skill does, which one fits their situation, or how to invoke one — including "what can paad do", "list the paad skills", "is there a paad skill for X", or a request for the arguments of a named paad skill.
release
Cut a paad release — pick the semver bump from what is in [Unreleased], run make release, merge, tag, and verify the published plugin.
backlog
EXPERIMENTAL. Use when working the project-wide out-of-scope backlog at paad/code-reviews/backlog.md — cleaning it of entries that are already fixed or gone, or picking the next entry and fixing it end-to-end. Not for producing backlog entries — that is /agentic-review — and not for reviewing a branch diff.
makefile
Use when creating or updating a Makefile for a project, especially when standard targets (build, test, lint, format, etc.) are missing or when modifying targets that may already be wired into other tooling. Not for debugging why a build fails.