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/ethics03/kgskill/kg-setupgit clone --depth 1 https://github.com/Ethics03/kgskillWhat 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.00008 | $0.00320 |
| Opus 5 | $0.00004 | $0.00160 |
| Sonnet 5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
kg-setup 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 2d 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
Configure the Knowledge Graph path. If a path argument was provided, use it directly. Otherwise check for existing config and report it, or search for a KG and prompt the user.
Steps
1. Check for existing config
Check in order:
$MYKG_PATHenvironment variable~/.config/mykg/configfile~/.mykgrcfile
If found, verify the path exists on disk:
- If it exists and contains
index.md: report✓ KG found at <path>and stop. - If the path doesn't exist: tell the user the configured path is missing and suggest
/kg-initto create it.
2. If no config found, search common locations
Check each of these for index.md + log.md:
~/MyKG~/Dev/Obsidian/MyKG~/Documents/MyKG~/Notes/MyKG~/vault/MyKG
If any are found, show them to the user and ask which to use.
3. If nothing found, ask the user
Ask: "No KG found. Enter a path to configure, or I can create one with /kg-init."
4. Save config
Once a path is confirmed:
mkdir -p ~/.config/mykg
echo "<path>" > ~/.config/mykg/config
Report ✓ Config saved. KG path: <path>.
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.
- 2d ago First seen · 44 lines · 8 tokens per session scan A f9add432aa19
kg-setup is a command published in the GitHub repository Ethics03/kgskill (3 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 320 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-31.
Other commands, from other repositories
code-review
The /plannotator-review slash command for reviewing local changes, comparing branches, or reviewing GitHub pull requests.
plan-review
The core plan review flow across Claude Code, Codex, and other supported agent hosts.
plannotator-last
Annotate the last rendered assistant message.
plannotator-review
Open interactive code review for current changes or a PR URL.
wiki-query
Query the LLM Wiki and synthesize an answer.
docs-builder
Reorg a docs corpus, split an oversized doc, search it, keep pages current, index them.