OpenKB is a command-line system that turns documents and other sources into a structured, linked wiki-style knowledge base using large language models. It is for organizing and retrieving information from long, varied documents, while the catalogue entries provide skills and instructions for working with it.
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 VectifyAI/OpenKB --skill openkb-html-criticgit clone --depth 1 https://github.com/VectifyAI/OpenKBWrote 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/vectifyai/openkb/openkb-html-critic)<a href="https://agentmods.dev/skills/vectifyai/openkb/openkb-html-critic"><img src="https://agentmods.dev/badge/skills/vectifyai/openkb/openkb-html-critic/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/vectifyai/openkb/openkb-html-critic"><img src="https://agentmods.dev/badge/skills/vectifyai/openkb/openkb-html-critic.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00132 | $0.01392 |
| Opus 5.5 | $0.00053 | $0.00557 |
| Sonnet 5.5 | $0.00026 | $0.00278 |
| Haiku 4.5 | $0.00013 | $0.00139 |
Grade A, and why
openkb-html-critic 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 1mo 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML deck critic
You are a senior front-end designer reviewing an already-generated single-file HTML deck. You did NOT write the deck — someone else did, and your job is to patch it for visual correctness without rewriting the content.
How this skill is invoked
The user (CLI: openkb deck new --critique, chat: /critique <path>)
points you at a single HTML file under output/. Read it, find issues
from the checklist below, and write the corrected version back in one
atomic write_file call (full file contents, never partial).
The path is in the user intent block above.
Checklist (run in order, report what you found)
1. CSS specificity — the #1 bug source
LLM-written deck CSS typically has:
.slide { display: none; ... }
.slide.active { display: flex; } /* or display: grid */
But then later defines slide-modifier classes:
.divider { display: flex; ... } /* ← BUG */
.center { display: flex; ... } /* ← BUG */
.q { display: flex; ... } /* ← BUG */
.hero { display: grid; ... } /* ← BUG */
Because .divider and .slide have the same specificity but the
modifier comes LATER in source order, .divider wins. Result: any
slide with class="slide divider" always displays, regardless of
the active class. Multiple slides stack on top of each other, the
deck appears to "not paginate".
Fix: strip display: <foo>; from any single-class selector that
matches a slide modifier (anything that appears in a <section class="slide X"> where X is the modifier name). The remaining
declarations (flex-direction, gap, alignment, background) stay. After
the patch, only .slide and .slide.active (or .active) control
the display property.
Quick scan: list every <section class="slide ..."> and collect the
extra class names. For each, find that class's CSS rule; if it has a
display: declaration, that's the bug. Fix all of them in one pass.
2. Navigation works
There should be JS that:
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.
- 1mo ago First seen · 141 lines · 132 tokens per session scan A 16f547511860
openkb-html-critic is a skill published in the GitHub repository VectifyAI/OpenKB (4,803 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 132 tokens to every session and 1,392 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
design-context-extract
Extract design DNA from app screenshots, live URLs, or screen recordings using Google Stitch — color palettes, typography, spacing tokens, component patterns, and motion specs as design-tokens.json or Tailwind config. Use when the user points to a screenshot, URL, or video and asks to extract or audit the design…
figma-design-handoff
Figma-to-code design handoff patterns including Figma Variables to design tokens pipeline, component spec extraction, Dev Mode inspection, Auto Layout to CSS Flexbox/Grid mapping, and visual regression with Applitools. Use when converting Figma designs to code, documenting component specs, setting up design-dev…
animation-motion-design
Animation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
component-search
Search 21st.dev component registry for production-ready React components. Finds components by natural language description, filters by framework and style system, returns ranked results with install instructions. Use when looking for UI components, finding alternatives to existing components, or sourcing design system…
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI).…