Borrowing it
Nothing to install: this file belongs to fokkerone/superspecs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fokkerone/superspecs/main/.skills/verify-wiki/SKILL.mdgit clone --depth 1 https://github.com/fokkerone/superspecsWrote 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/fokkerone/superspecs/verify-wiki)<a href="https://agentmods.dev/skills/fokkerone/superspecs/verify-wiki"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/verify-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/fokkerone/superspecs/verify-wiki"><img src="https://agentmods.dev/badge/skills/fokkerone/superspecs/verify-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.00075 | $0.02259 |
| Opus 5 | $0.00037 | $0.01130 |
| Sonnet 5 | $0.00015 | $0.00452 |
| Haiku 4.5 | $0.00007 | $0.00226 |
Grade A, and why
verify-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 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.
How it starts
The opening of the file, as written. The whole thing — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: verify-wiki
You are distilling the completed feature into the living project wiki.
The feature works. The tests pass. Now you extract the knowledge that should survive beyond this session — so future planning, future features, and future sessions start informed.
The wiki lives at superspec/wiki/ and doubles as an Obsidian vault. Write every page to be navigable in Obsidian: use [[wikilinks]] for internal links, YAML frontmatter with tags:, and keep each page focused on a single knowledge unit.
What to distill (and what not to)
Distill:
- Architecture decisions (what was chosen and why)
- Patterns discovered or established
- Trade-offs made (what was given up, what was gained)
- Gotchas (things harder than expected + how they were solved)
- Key interfaces / contracts / data shapes
- Open questions deferred to future work
Do NOT copy:
- Full code listings (reference file paths instead)
- Task checklists or execution logs
- The full spec (it lives in
superspec/specs/)
Provenance
Mark the origin of every claim so future readers know what is fact vs. synthesis:
- Default (no marker): directly extracted from source material
^[inferred]— synthesized by the agent; not stated verbatim in sources^[ambiguous]— sources disagree or the claim is uncertain
Example:
The team chose Redis over Postgres for session storage because of latency requirements.
A TTL of 15 minutes was selected as the balance point. ^[inferred]
Note: the DISCUSS.md mentions 10 minutes but the spec says 15 — see review-log. ^[ambiguous]
Steps
1. Gather the source material
Read:
superspec/specs/<slug>/DISCUSS.mdsuperspec/specs/<slug>/spec.mdsuperspec/phases/<slug>-execute/review-log.md- The implementation itself (key files touched)
2. Scan existing wiki pages first
Before writing anything new, scan the existing wiki for related content.
superspec/wiki/
├── Home.md ← read first: domain index
├── log.md ← read: recent activity
└── <domain>/
├── Home.md ← domain index
└── *.md ← existing knowledge pages
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 · 320 lines · 75 tokens per session scan A 03d6946f15d4
verify-wiki is a skill published in the GitHub repository fokkerone/superspecs (4 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 2,259 once invoked, about $0.0004 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
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…