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 christianb93/WikiSpec --skill wikispec-wikigit clone --depth 1 https://github.com/christianb93/WikiSpecWrote 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/christianb93/wikispec/wikispec-wiki)<a href="https://agentmods.dev/skills/christianb93/wikispec/wikispec-wiki"><img src="https://agentmods.dev/badge/skills/christianb93/wikispec/wikispec-wiki.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.1 | $0.00034 | $0.01335 |
| Opus 5 | $0.00017 | $0.00668 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
wikispec-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 7d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki Schema
A knowledge base that helps humans and agents to maintain the code base, to understand designs, technical concepts, key features and key dependencies.
Overview
This wiki synthesizes knowledge built while working on the code in this software project. It focuses on key relations, concepts and facts and organizes for use by coding agents and human developers.
You maintain the wiki incrementally. When sources need to be ingested you read them, extract key concepts, and integrate them into the existing structure. The wiki becomes richer with every addition.
Directory Structure
This wiki is part of the overall wikispec structure.
wikispec/ ← the wikispec root directory, located in the project root
├── changes/
│ ├── active/ ← changes currently in progress
│ └── archived/ ← completed and archived changes
└── wiki/ ← the wiki - these instructions focus on how to maintain this
├── <topic 1>/ ← documentation for one topic
├── .../
├── <topic n>/
├── log.md ← append-only log of operations on the wiki
└── index.md ← index page
Wiki topics
The wiki is organized in topics, that correspond to subdirectories of wikispec/wiki. You can use the wikispec CLI that exists in the path (no need to install) to understand which topics exist. Running
wikispecs topics
returns a JSON structure with a list of all topics and their description.
Operations
Ingest a change
When a change needs to be a ingested, follow these steps.
- Understand the change
- locate specification, design and tasks for this change by running
wikispec files --change. This will return a list of specification, design documents and tasks that describe the change - look at the tasks and design documents to determine which source files have been added or changed as part of this change
- Read them. Understand the change
- Determine impact on wiki
- run
wikispec topicsto get a list of existing topics and their descriptions - identify topics which could be impacted by this change, using your own judgement and the instructions printed by the
wikispec topicstool - look at the files in the directory (pages) and identify which pages need to be updated or created
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.
- 7d ago First seen · 158 lines · 34 tokens per session scan A ad9bacbdc6ab
wikispec-wiki is a skill published in the GitHub repository christianb93/WikiSpec (4 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 1,335 once invoked, about $0.0002 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
i18n-parity
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change…
file-headers
MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use automatically whenever writing a new file or editing an existing one; do…
productivity-score
Calculate a productivity score using actual Agent Monitor metrics — session completion rates, cache efficiency (cacheread vs input), compaction pressure (baseline tokens), turn velocity (turncount / totalturndurationms), tool success ratio (PreToolUse vs PostToolUse), and the workflow intelligence API's complexity and…
budget-set
Define a spend budget for Claude Code and, optionally, create a cost alert rule that fires when usage crosses the limit, via POST /api/alerts/rules on the Agent Monitor dashboard. Reads current spend from /api/pricing/cost to size the budget sensibly and explains every rule field before writing. Use when setting a…
dashboard-status
Quick dashboard health and status overview — checks the Agent Monitor API (port 4820), reports session/agent/event counts from /api/stats, confirms WebSocket connectivity, reads the redacted hook status returned by /api/settings/info, and shows data freshness (last event timestamp). Use to verify the monitoring system…
run-agent
Launch and supervise Claude Code or Codex through the CCAM Run API. Use when the user wants to start a monitored agent, select a model, approval policy, sandbox, or working directory, send a follow-up, inspect live output, resume a native session, or stop a dashboard-launched run.