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 agentmods add skills/nemock/company-brain/visualizenpx skills add nemock/company-brain --skill visualizegit clone --depth 1 https://github.com/nemock/company-brainWrote 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/nemock/company-brain/visualize)<a href="https://agentmods.dev/skills/nemock/company-brain/visualize"><img src="https://agentmods.dev/badge/skills/nemock/company-brain/visualize.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 | $0.00096 | $0.01154 |
| Opus 5 | $0.00048 | $0.00577 |
| Sonnet 5 | $0.00019 | $0.00231 |
| Haiku 4.5 | $0.00010 | $0.00115 |
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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
visualize
This skill turns the typed graph into an interactive HTML page. Force-directed D3 layout, color by node type, hover for tooltip, click for details. Single file, single command. No server, no database.
You do not visualize the controlled-document space. You do not invent edges. The viewer reflects what is in the vault.
Before any render
- Confirm the vault path. Default: current working directory. Refuse if
_system/PROFILE.mdis missing. - Run
cb validate --path <vault>first. Broken edges show as missing nodes in the viewer — clean validate first so the layout reflects the real graph. - Confirm the active profile. The
ifu-chainandpredicate-treeview modes require the medical-device profile.
Capabilities
cb viewer (default mode: graph)
cb viewer --path <vault> # → <vault>/vault-graph.html
cb viewer --path <vault> --out ~/some-graph.html # custom output path
The default mode renders every node and every link in the vault. Nodes are colored by type with an inline legend. Edges follow the typed edge set (derived_from, supports, preceded_by, related_to, etc.). Hover any node for title + summary; click for full detail in the side panel; drag to reposition; scroll to zoom.
IFU history chain (medical-device)
cb viewer --path <vault> --mode ifu-chain --out exports/ifu-chain.html
Only indication-for-use nodes appear, connected via preceded_by / followed_by edges. Use this for IFU evolution questions: "how did CardioTrace's IFU shift between their two 510(k)s?" The answer is the chain walk.
510(k) predicate tree (medical-device)
cb viewer --path <vault> --mode predicate-tree --out exports/predicate-tree.html
Only regulatory-clearance nodes, connected via preceded_by (the predicate citation). Use this for substantial-equivalence questions: "which competitor clearances do our planned filings cite as predicates, and how deep does that chain go?"
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 First seen · 75 lines · 0 tokens per session scan A e82b3e6dbbb7
visualize is a skill published in the GitHub repository nemock/company-brain (5 stars, last pushed 3mo ago), licensed MIT. It adds 96 tokens to every session and 1,154 once invoked, about $0.0005 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
mykg
Run mykg knowledge-graph commands inside Claude Code from one slash command /mykg. The user describes intent in natural language (extract, append, sync, resume, approve, walkthrough, parse-docs, fetch-web, query); the skill parses intent, builds the right mykg CLI command from the live --help output, confirms, runs…
mykg-github-pages
Set up and maintain the GitHub Pages site for the mykg repo (SenolIsci/mykg) — a purpose-built pages/ folder (landing page adapted from README.md, blog posts, diagrams), built by a GitHub Actions workflow that runs Jekyll and deploys the result to a gh-pages branch. Use whenever the user wants to publish project…
networkx
Build, analyze, and visualize networks and graphs using NetworkX (Python). Use this skill whenever the user wants to: create graphs or networks, analyze graph properties, compute centrality measures, find shortest paths, detect communities, run graph algorithms, convert graphs to/from matrices or dataframes, visualize…
design-architecture
Reviews the current codebase architecture and proposes improvements using four parallel specialist subagents: System Architect, Software Architect, Data Architect, and an Adversarial Architect that red-teams failure paths, LLM adversarial output scenarios, silent corruption risks, and invariant bypasses. Each subagent…
agent-recall
Persistent compounding memory for AI agents. 5 default MCP tools: sessionstart, sessionend, remember, recall, check. Full surface (18 tools) available with --full flag. Two-verb model: inhale (sessionstart) and exhale (sessionend). Correction-first memory with decision trail tracking, watchfor warnings, palace rooms…
swarmvault
Use SwarmVault when the user needs a local-first knowledge vault that writes durable markdown, graph, search, dashboard, review, chat-session, context-pack, task-ledger, static AI export, retrieval, and MCP artifacts to disk from books, notes, transcripts, exports, datasets, slide decks, files, URLs, code, and…