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 skills add robertguss/claude-code-toolkit --skill project-wikigit clone --depth 1 https://github.com/robertguss/claude-code-toolkitWrote 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/skills/robertguss/claude-code-toolkit/project-wiki)<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/project-wiki"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/project-wiki/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/robertguss/claude-code-toolkit/project-wiki"><img src="https://agentmods.dev/badge/skills/robertguss/claude-code-toolkit/project-wiki.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.01284 |
| Opus 5.5 | $0.00020 | $0.00514 |
| Sonnet 5.5 | $0.00010 | $0.00257 |
| Haiku 4.5 | $0.00005 | $0.00128 |
Grade A, and why
project-wiki 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 29d 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project wiki
A wiki is a persistent, compounding record: interlinked markdown pages the agent
writes and maintains and the human reads. Knowledge is compiled once and kept
current, so every page already carries its cross-references, its contradictions,
and its place in the whole. The pattern is Karpathy's
(references/karpathy-llm-wiki.md); this
skill is its shape for a repo.
Three layers, all inside the repo:
- Raw sources (
raw/): immutable. Read, never edited. Corrections go on wiki pages. - The wiki: the pages. Written by the agent only. In a project run by the
leadskill, the lead writes them and the worker never does. - The schema (
SCHEMA.md): the page types, frontmatter, tag taxonomy, and conventions. The agent and the human co-evolve it; a convention changes there first, then on the pages.
Two presets, chosen at init: project record (plans, sessions, decisions, a roadmap board, a standing synthesis, maps) for a repo being built, and research vault (sources, entities, concepts, comparisons, filed queries) for a topic being studied. Both share the operations below.
Start of session
Read, in order: SCHEMA.md whole, index.md, the last 20 entries of log.md
(grep "^## \[" log.md | tail -20 finds them). In a project record, also the
synthesis page and the roadmap board. Only then touch a page.
No SCHEMA.md in the repo means the wiki does not exist yet: follow
references/init.md.
Operations
Ingest
A source arrives (a URL, a file, a pasted transcript, a worker's report).
- Save it under
raw/<kind>/with frontmatter (source_url,ingested, andsha256of the body), named by what it is and when. - Find what already exists: search
index.mdand the pages for every entity, concept, or step the source names. This is the difference between a wiki and a pile of duplicates. - Write or update pages by the schema's thresholds: a page when a thing appears
in two sources or is central to one, an update when it is already covered,
nothing for a passing mention. Every page carries frontmatter from the
schema, two or more outbound
[[wikilinks]], and a## Relatedlist. New information that contradicts a page keeps both claims with dates, markscontested: trueandcontradictions:on both, and names the pair for the human. - Update
index.mdfor new pages and append onelog.mdentry naming every file touched.
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/index.md 552 B
- assets/lint.py 5.2 KB runs code
- assets/log.md 417 B
- assets/publish-wiki.yml 1.1 KB
- assets/quartz.config.yaml 6.5 KB
- assets/SCHEMA-project-record.md 7.4 KB
- assets/SCHEMA-research-vault.md 4.7 KB
- README.md 3.2 KB
- references/init.md 2.1 KB
- references/karpathy-llm-wiki.md 12 KB
- references/publish.md 1.7 KB
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.
- 29d ago First seen · 119 lines · 49 tokens per session scan A df9fa5e9198a
project-wiki is a skill published in the GitHub repository robertguss/claude-code-toolkit (126 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 1,284 once invoked, about $0.0002 per session on Opus 5.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-09-17.
Other skills, from other repositories
unit-lane
One-shot lane conductor for a delivery unit: triage, implement, evidence, and close in a single document. Triggers: "unit-lane", "run the lane", "work on this feature/fix", "build this unit".
workflow-status
Read-only workflow sensor: run the deterministic script, read the fixed machine envelope, interpret the recommendation. Never edits. Triggers: "workflow-status", "workflow status", "what can I build next".
offensive-vuln-classes
Exploit development curriculum covering core vulnerability classes with real-world CVE case studies: stack/heap buffer overflows, use-after-free, integer overflows, format strings, type confusion, and race conditions. Use when learning or teaching vuln classes, researching specific CVE patterns, or building exploit…
offensive-mitigations
Security mitigation reference and bypass catalog: ASLR, DEP/NX, RELRO, stack canaries, CFI, sandboxing, seccomp. Covers both detection of enabled mitigations and known bypass techniques. Use when assessing target hardening or planning exploit mitigation bypasses.
offensive-exploit-development
Exploit development operational guide: environment setup, debugging workflow, PoC development lifecycle, writing reliable exploits, using pwntools/pwndbg, heap exploitation techniques, and weaponization considerations. Use when actively developing exploits or setting up an exploit dev environment.
offensive-k8s-attacks
Kubernetes cluster attack techniques covering the full attack lifecycle from initial foothold in a pod to cluster-wide compromise. Covers service account token theft and impersonation, RBAC misconfiguration exploitation including wildcard permissions and privilege escalation via role binding, direct etcd access for…