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/ethics03/kgskill/initnpx skills add Ethics03/kgskill --skill initgit 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.00023 | $0.00418 |
| Opus 5 | $0.00012 | $0.00209 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
project-skill 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
[PROJECT NAME] Skill
Project-specific instructions for the Knowledge Graph.
Project Overview
[Brief description of the project, domain, or topic]
Domain
[What domain is this project about? Examples:
- Research: "Quantum computing research"
- Reading: "The Lord of the Rings"
- Personal: "Health and fitness tracking"
- Code: "Codebase documentation" ]
Source Types
[What types of sources will be ingested?]
- Articles
- Papers
- Transcripts
- Notes
- [Other]
Key Entities
[What kinds of entities are relevant to this domain? Examples:
- People, organizations, tools, places
- Characters, locations, items
- Concepts, frameworks, methods ]
Key Concepts
[What concepts are central to this domain?]
Ingestion Workflow
[Custom steps for ingesting sources in this domain]
- Read source
- Extract entities and concepts
- Create/update wiki pages
- Note contradictions with existing knowledge
- Update index and log
Page Types
[Project-specific page types beyond the standard entities/concepts/synthesis]
Conventions
[Project-specific naming and formatting conventions]
File Naming
- Entities:
entity-name.md - Concepts:
concept-name.md - Sources:
source-title-slug.md
Cross-References
- Link to related entities:
[[entities/Related]] - Link to concepts:
[[concepts/Topic]]
Current Focus
See [[../Active.md]] for current focus items.
Key Files
| File | Purpose |
|---|---|
raw/ |
Source documents |
wiki/entities/ |
Entity pages |
wiki/concepts/ |
Concept pages |
wiki/synthesis/ |
High-level summaries |
../Active.md |
Current priorities |
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 · 84 lines · 23 tokens per session scan A 8ac657bda0f2
project-skill is a skill published in the GitHub repository Ethics03/kgskill (3 stars, last pushed 4mo ago), licensed MIT. It adds 23 tokens to every session and 418 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 skills, from other repositories
plannotator-compound
Analyze a user's Plannotator plan archive to extract denial patterns, feedback taxonomy, evolution over time, and actionable prompt improvements — then produce a polished HTML dashboard report. Falls back to Claude Code ExitPlanMode denial reasons when Plannotator data is unavailable.
release-plannotator
Prepare and execute a Plannotator release — draft release notes with full contributor credit, bump versions across all package files, build in dependency order, and kick off the tag-driven release pipeline. Use this skill whenever the user mentions preparing a release, bumping versions, writing release notes, tagging…
plannotator
Reference for using the Plannotator CLI: plan review, code review, annotating files, URLs, folders, and running local apps, annotating the last assistant message, browsing archived plan decisions, and exporting or sharing Guided Reviews. Invoke when asked to use Plannotator for anything not covered by a more specific…
update-deps
Audit and update npm/Bun dependencies with supply chain integrity checks — verifies maintainers, publish age, tarball diffs, and provenance before bumping. Defers risky packages to /.supply-chain/notes/.
plannotator-visual-explainer
Generate self-contained HTML visualizations with Plannotator theming. Use for implementation plans, PR explainers, architecture diagrams, data tables, slide decks, and any visual explanation of technical concepts. Plans and PR explainers follow Plannotator's prescriptive approach; all other visual content delegates to…
review-renovate
Review Renovate bot PRs that update GitHub Actions dependencies. Verifies supply chain integrity by checking pinned commit SHAs against upstream tagged releases, reviews changelogs for breaking changes, and confirms compatibility with existing workflow configurations. Use when a Renovate PR updates GitHub Actions in…