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 evergreen-it-dev/folio --skill folio-boardsgit clone --depth 1 https://github.com/evergreen-it-dev/folioWrote 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/evergreen-it-dev/folio/folio-boards)<a href="https://agentmods.dev/skills/evergreen-it-dev/folio/folio-boards"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-boards/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/evergreen-it-dev/folio/folio-boards"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-boards.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.00041 | $0.03011 |
| Opus 5.5 | $0.00016 | $0.01204 |
| Sonnet 5.5 | $0.00008 | $0.00602 |
| Haiku 4.5 | $0.00004 | $0.00301 |
Grade A, and why
Folio Boards 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 6d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Excalidraw boards through create_board/update_board
A board (kind: board) is a separate page in the tree of a space, a
full-screen Excalidraw. The agent does not draw every element of the scene
by hand — it describes the board with the compact sketch DSL, and the
server lays it out into real Excalidraw elements itself.
When to use a board, and when mermaid in a document
- A simple diagram inside a document (a flowchart, sequence, gantt and so
on) is handier and cheaper as a ```mermaid block right in the body of the
page (the
folio-contentskill, section "Mermaid diagrams"): it creates no separate page, is easily edited as text, is versioned as a line in git. - A board — when exactly a separate diagram page in the tree is needed (an architecture, a map of a process that people want to open and refine by hand in the Excalidraw editor), or when "make a board" is asked for explicitly.
The contract of create_board / update_board
create_board({ space, parentPath, title, sketch? | scene? })
update_board({ id, sketch? | scene? })
Pass sketch — the compact DSL below. Use the full scene (raw Excalidraw
elements) only for a pinpoint edit of an already existing board: first
read_page (for a board it returns scene), then make changes in the array
of elements you got, and send it back through update_board({ id, scene }).
Do not generate a scene from scratch — it is the format of the Excalidraw
engine, not a DSL that is convenient to write.
The sketch DSL
sketch = {
background?: string, // hex of the board background, '#ffffff' by default
nodes: [{
id: string, // unique within the sketch, referenced by edges/frame
type: 'rectangle' | 'ellipse' | 'diamond' | 'text' | 'frame',
label?: string,
x: number,
y: number,
w?: number, // the default depends on the type, see below
h?: number,
color?: string, // stroke, hex, default '#1e1e1e'
background?: string, // fill hex or 'transparent'
fontSize?: 16 | 20 | 28,
frame?: string, // id of the type:'frame' node this node lies in
}],
edges: [{
id?: string,
from: string, // id of the source node
to: string, // id of the target node
label?: string,
elbowed?: boolean, // default true — orthogonal (elbow) arrows
start?: 'arrow' | null, // default null
end?: 'arrow' | null, // default 'arrow'
color?: string,
}],
}
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.
- 6d ago First seen · 223 lines · 41 tokens per session scan A bb072f364252
Folio Boards is a skill published in the GitHub repository evergreen-it-dev/folio (69 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 3,011 once invoked, about $0.0002 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-10-09.
Other skills, from other repositories
solomd
Read, search, edit, and version-control any folder of Markdown notes via the SoloMD MCP server. 13 tools including AutoGit per-note history, semantic search, and write-with-sandbox via an accept/reject branch. Includes 11 starter agent recipes (weekly review, todo extract, link suggester, …).
github
A writing guide for GitHub issues, pull requests, code reviews, and release notes in Zhin projects. GitHub is a service where teams track bugs, discuss changes, review code, and publish project updates.
excalidraw-diagram
Create Excalidraw diagrams as editable .excalidraw JSON that make a visual argument — architecture, flowchart, sequence, state, ER, timeline, swimlane, quadrant, loop/flywheel, layers, nested, tree, org chart, venn, pyramid, process, medallion, data flow, IT current-state, evidence/protocol explainers, before/after…
hyalo-changelog
Maintain Keep a Changelog files with Hyalo's changelog profile and add/release commands.
tela-wiki
Use when the user asks something their team's own documentation would answer, or asks to write or update a page, spreadsheet, or slide deck in their tela wiki.
changelog
Generate, update, review, and maintain changelogs using Keep a Changelog format, semantic-release, and conventional commits. Use this skill whenever the user wants to add a changelog entry, prepare release notes, document version changes, generate a changelog from git history, configure semantic-release, understand…