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-projectgit clone --depth 1 https://github.com/Ethics03/kgskillWrote 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/ethics03/kgskill/kg-project)<a href="https://agentmods.dev/commands/ethics03/kgskill/kg-project"><img src="https://agentmods.dev/badge/commands/ethics03/kgskill/kg-project.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.00011 | $0.00601 |
| Opus 5 | $0.00005 | $0.00300 |
| Sonnet 5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
kg-project 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
Create a new project folder in the Knowledge Graph. The argument is the project name; an optional second argument is a description.
Steps
1. Resolve KG path
Check in order: $MYKG_PATH env var → ~/.config/mykg/config → ~/.mykgrc → common locations (~/MyKG, ~/Dev/Obsidian/MyKG). If not found, tell the user to run /kg-setup first.
2. Validate project name
If no name was provided, tell the user: Usage: /kg-project <name> [description] and stop.
Normalize the name: replace spaces with hyphens, keep only alphanumeric and hyphens.
3. Check if already exists
If <KG_PATH>/<project-name>/ already exists, tell the user and stop.
4. Create project structure
Run:
mkdir -p <KG_PATH>/<name>/{Architecture,Decisions,Plans,Analysis}
5. Write Decisions/README.md
# Decisions
Architecture Decision Records (ADRs) for <name>.
## Index
| ADR | Title | Status | Date |
|-----|-------|--------|------|
## Next ADR Number
**Next: 001**
## Creating a New ADR
1. Update the number above
2. Create `ADR-XXX - Title.md`
3. Fill in: Context, Decision, Consequences, Alternatives
4. Update this index
5. Update root `index.md`
6. Add entry to root `log.md`
6. Write SKILL.md
---
name: <name>-skill
description: Project-specific instructions for <name>. Use when working on this project.
---
# <name>
## Project Overview
<description>
## Tech Stack
| Component | Technology |
|-----------|------------|
## Key Architecture Decisions
Refer to ADRs in [[Decisions/]].
## Current Priorities
See [[Active]] for current focus items.
## Project Conventions
- [Add conventions]
## Key Files
| File | Purpose |
|------|---------|
| `Architecture/Overview.md` | System design |
| `Decisions/README.md` | ADR index |
7. Update root index.md
Add the project to the Projects table:
| [[<name>/]] | <description> |
8. Append to root log.md
## [YYYY-MM-DD] project | Create <name>
- Created project [[<name>/]]
9. Report
Tell the user the project was created, show the path and structure, and suggest next steps: edit SKILL.md with project details, create Architecture/Overview.md.
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 · 112 lines · 11 tokens per session scan A 88d7b4e1cd78
kg-project is a command published in the GitHub repository Ethics03/kgskill (3 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 601 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-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.