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-archivegit 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-archive)<a href="https://agentmods.dev/skills/christianb93/wikispec/wikispec-archive"><img src="https://agentmods.dev/badge/skills/christianb93/wikispec/wikispec-archive.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.00009 | $0.00260 |
| Opus 5 | $0.00005 | $0.00130 |
| Sonnet 5 | $0.00002 | $0.00052 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
wikispec-archive 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 8d 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
Skill: wikispec-archive
Drive the agent through the full archive step for a wikispec change. You will use the wikispec tool which is a binary in the path, no need to install anything.
Steps
-
Determine the change name.
- If the user provided a change name, use it exactly.
- If no name is provided and no description is provided, assume that we will resume work on an existing active change. Use
wikispec listto list all active changes. If there is only one name, assume that we will be working on this one, otherwise ask the user. Then skip step 2 (creation of the change) and proceed directly to step 3.
-
Follow instructions in a loop. Repeat until the step is complete:
wikispec instructions --change <name> --step archive- If the output contains instructions, follow them, then call the command again.
- If the output signals that the step is already complete, stop looping and inform the user that the archive step is done and the implementation of the change is complete
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.
- 8d ago First seen · 25 lines · 9 tokens per session scan A ad79af986df8
wikispec-archive is a skill published in the GitHub repository christianb93/WikiSpec (4 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 260 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 skills, from other repositories
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.
sprint-summary
Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turncount, turndurationms), and tool diversity across the sprint.
cwd-rollup
Roll up Claude Code sessions by working directory (project) from Agent Monitor data — session count, total cost, total tokens, and last-active timestamp per cwd — so per-project activity can be compared at a glance. Use when summarizing where effort and spend went across projects.
daily-standup
Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turncount, totalturndurationms).
run-history
Inspect CCAM dashboard-run history and relate live run handles to persisted Claude Code or Codex sessions. Use when finding a prior launched task, checking whether a run is still attached, reviewing start/end status, or deciding whether to resume, view, or relaunch work.
refine-ticket
Refine a development ticket — or brainstorm a raw idea — into a validated, self-contained REQUIREMENTS document — the "what", verified against the codebase. Invoke manually only.