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 scaccogatto/okf-skills --skill visualizegit clone --depth 1 https://github.com/scaccogatto/okf-skillsWrote 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/scaccogatto/okf-skills/visualize)<a href="https://agentmods.dev/skills/scaccogatto/okf-skills/visualize"><img src="https://agentmods.dev/badge/skills/scaccogatto/okf-skills/visualize.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- 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.00111 | $0.00768 |
| Opus 5 | $0.00056 | $0.00384 |
| Sonnet 5 | $0.00022 | $0.00154 |
| Haiku 4.5 | $0.00011 | $0.00077 |
Grade A, and why
visualize 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 4d 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
Visualize an OKF bundle
Generate a self-contained HTML graph of the target bundle. The bundle directory
is required, so pass .okf explicitly when no path is given. No backend, no
install, no bundle content leaves the page. The viewer does need network
access: cytoscape, marked and dompurify load from cdn.jsdelivr.net.
uv run "${CLAUDE_SKILL_DIR}/scripts/okf_visualize.py" $ARGUMENTS
If uv is unavailable:
python3 -m pip install --quiet pyyaml && \
python3 "${CLAUDE_SKILL_DIR}/scripts/okf_visualize.py" $ARGUMENTS
The detail panel shows each concept's type, description, tags, status,
generated, verified, stale_after, sources (with their credibility
signals, a usage_count alongside the usage_window that frames it), and
rendered body; a sources entry pointing at another concept in the bundle also
becomes a graph edge. A v0.1 timestamp is read as generated.at, so legacy
bundles still render fully.
Two badges are derived, not read: the §5.3 trust tier
(unverified / machine-confirmed / human-reviewed, keyed off the human:
prefix in verified[].by) and staleness (today >= stale_after). They are
advisory signals — when reporting on a bundle, say which tier a concept is in
rather than treating any of them as a gate.
| Flag | Effect |
|---|---|
-o <path> |
Output file (default <bundle>/viz.html). |
-t, --title |
Graph title (default parent/bundle dir name). |
-l, --link |
Source URL shown in the header. |
--layout |
cose, concentric, breadthfirst, circle, grid. |
--max-nodes N |
Exit 1 above N concepts (useful in CI). |
--og-image URL |
Absolute URL for the social preview image. |
Above 1,000 concepts the default switches to concentric (force freezes the
page; --layout cose overrides, and the in-page picker asks first). Above
5,000 it warns that the page loads slowly and reads as a hairball, and
suggests rendering a subdirectory.
Open it in any browser; ${CLAUDE_SKILL_DIR} resolves whether this runs as part
of the okf plugin or as a standalone skills.sh skill. The page is
deep-linkable: ?select=<concept-id> or #<concept-id> opens that concept,
?layout=<name> presets the layout.
What ships with it
1 file 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.
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.
- 4d ago Changed · +16 lines · +3 tokens per session 37a0a60d07d0
- 8d ago First seen · 49 lines · 108 tokens per session scan A 2e79505c1fe4
visualize is a skill published in the GitHub repository scaccogatto/okf-skills (373 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 768 once invoked, about $0.0006 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-30.
Other skills, from other repositories
planning-with-scratchpad
Use when user explicitly requests planning with a scratchpad, or asks for persistent tracking of a complex task that the human can browse visually. Backs planning files with the scratch CLI so a pad's files are registered and viewable.
scratch
Organize knowledge from an agent session into a scratchpad — a folder of files plus a scratchpad.json manifest. Use when a task generates notes, snippets, command output, diagrams, or artifacts worth keeping together for a session/activity.
init
Initialize a personal Trove, a local file-based knowledge index for Claude Code. Use when the user says start/set up/create my trove, or when they want to remember things but no trove exists yet. Scaffolds the trove directory, INDEX.md and entries/ folder at user scope (/.claude/trove, follows you everywhere) or…
remember
Capture a durable learning into the personal Trove. Use when the user says remember this, note this, save to trove, add to my trove, or when a session surfaces a decision, gotcha, convention/preference, or external reference worth keeping. Writes one atomic entry file and updates INDEX.md.
query
Progressive retrieval from the Trove index. Use when the user asks what Trove knows about a subsystem, where code lives, or wants context assembled before editing. Runs architecture -> subsystem -> module -> symbol retrieval with a context budget.
index
Index the repository into Trove memory layers (symbols, modules, subsystems, architecture). Use when the user asks to index the repo, build the trove index, refresh symbols, or re-index after large changes.