json-canvas

json-canvas is a skill for Claude Code from michaeljauk/brain-starter. It costs 54 tokens per session (2,225 once invoked), scanned A, a copy of json-canvas, MIT.

A file format and workflow for making visual canvases, such as mind maps and flowcharts, in Obsidian. It stores boxes, groups, and the lines connecting them in a .canvas JSON file.

In plain words
What is it for?
Create new Obsidian canvases, edit existing ones, add nodes and connections, and check that the JSON and references are valid.
Why use it?
It helps keep canvas files valid and connected, so nodes do not overlap unnecessarily and links do not point to missing items.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Create new Obsidian canvases, edit existing ones, add nodes and connections, and check that the JSON and references are valid.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michaeljauk/brain-starter/json-canvas
Install

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.

Any agent
npx skills add michaeljauk/brain-starter --skill json-canvas
Clone the repo
git clone --depth 1 https://github.com/michaeljauk/brain-starter

Made for: Claude Code.

Wrote 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.

agentmods badge for json-canvas

README.md
[![agentmods](https://agentmods.dev/badge/skills/michaeljauk/brain-starter/json-canvas/github.svg)](https://agentmods.dev/skills/michaeljauk/brain-starter/json-canvas)
Your own site
<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/json-canvas"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/json-canvas/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.

agentmods 80×15 button for json-canvas

Your own site · 80×15
<a href="https://agentmods.dev/skills/michaeljauk/brain-starter/json-canvas"><img src="https://agentmods.dev/badge/skills/michaeljauk/brain-starter/json-canvas.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,225 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.02225
Opus 5.5 $0.00022 $0.00890
Sonnet 5.5 $0.00011 $0.00445
Haiku 4.5 $0.00005 $0.00222

Measured 1mo ago against content hash 873647521c5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

json-canvas 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.

Origin

This is a copy

100% identical to json-canvas — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/json-canvas/SKILL.md · 245 lines

How it starts

The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.

JSON Canvas Skill

File Structure

A canvas file (.canvas) contains two top-level arrays following the JSON Canvas Spec 1.0:

{
  "nodes": [],
  "edges": []
}
  • nodes (optional): Array of node objects
  • edges (optional): Array of edge objects connecting nodes

Common Workflows

1. Create a New Canvas

  1. Create a .canvas file with the base structure {"nodes": [], "edges": []}
  2. Generate unique 16-character hex IDs for each node (e.g., "6f0ad84f44ce9c17")
  3. Add nodes with required fields: id, type, x, y, width, height
  4. Add edges referencing valid node IDs via fromNode and toNode
  5. Validate: Parse the JSON to confirm it is valid. Verify all fromNode/toNode values exist in the nodes array

2. Add a Node to an Existing Canvas

  1. Read and parse the existing .canvas file
  2. Generate a unique ID that does not collide with existing node or edge IDs
  3. Choose position (x, y) that avoids overlapping existing nodes (leave 50-100px spacing)
  4. Append the new node object to the nodes array
  5. Optionally add edges connecting the new node to existing nodes
  6. Validate: Confirm all IDs are unique and all edge references resolve to existing nodes

3. Connect Two Nodes

  1. Identify the source and target node IDs
  2. Generate a unique edge ID
  3. Set fromNode and toNode to the source and target IDs
  4. Optionally set fromSide/toSide (top, right, bottom, left) for anchor points
  5. Optionally set label for descriptive text on the edge
  6. Append the edge to the edges array
  7. Validate: Confirm both fromNode and toNode reference existing node IDs

4. Edit an Existing Canvas

  1. Read and parse the .canvas file as JSON
  2. Locate the target node or edge by id
  3. Modify the desired attributes (text, position, color, etc.)
  4. Write the updated JSON back to the file
  5. Validate: Re-check all ID uniqueness and edge reference integrity after editing

Read the full file on GitHub · 245 lines

Changes

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.

  1. 1mo ago First seen · 245 lines · 54 tokens per session scan A 873647521c5b

Subscribe to this mod's changes

json-canvas is a skill published in the GitHub repository michaeljauk/brain-starter (5 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 2,225 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to json-canvas, differing in 4 lines, and is treated as a copy.

Related

Other skills, from other repositories

jtbd-to-interface

A method for turning user jobs—the outcomes people need to achieve—into a screen and navigation specification.

dzhokhov/markdown-agent-vault-ru · 272 tokens

ui-ux-pro-max

UI/UX design intelligence with 50+ styles, 161 palettes, 57 font pairings, 99 UX guidelines, and 25 chart types. Searchable database with priority-based recommendations for web and mobile.

assafkip/kipi-system · 50 tokens

obsidian-md2wechat

Format the current Obsidian article with the existing md2wechat CLI and return its preview to the Obsidian publishing plugin. Use when the user asks to typeset an Obsidian note for WeChat.

geekjourneyx/obsidian-md2wechat · 49 tokens

pkm-session-end

Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.

AdrianV101/obsidian-pkm-plugin · 49 tokens

pkm-write

Use when writing to the vault — creating new notes (vaultwrite), editing existing notes (vaultedit, vaultappend, vaultupdatefrontmatter). Handles duplicate checking, link discovery, annotations, and index updates for new notes. Provides guidelines for modifications.

AdrianV101/obsidian-pkm-plugin · 54 tokens

pkm-explore

Use when researching what the vault knows about a topic — performs graph + semantic exploration with gap analysis to map existing knowledge and find missing connections. Primarily used via the vault-explorer agent. Not for routine session-start context loading (hooks handle that).

AdrianV101/obsidian-pkm-plugin · 55 tokens