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-mcpgit 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-mcp)<a href="https://agentmods.dev/skills/evergreen-it-dev/folio/folio-mcp"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-mcp/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-mcp"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-mcp.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.00030 | $0.02035 |
| Opus 5.5 | $0.00012 | $0.00814 |
| Sonnet 5.5 | $0.00006 | $0.00407 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
Folio MCP 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 today.
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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The internal Folio MCP
Use this skill for any work with Folio spaces, pages, boards and data
tables. These are the same tools that are registered in server/mcp.ts
(buildFolioMcpServer) and available through the public /mcp with a PAT
token — the built-in chat gets them in-process, with the rights and the
audit of the current user of the session, without a separate token.
The order of work
- Find the entity:
search_pagesorlist_tree— do not guess theidof a page. - Read it:
read_page(a document/board) orfolio_table_schema+folio_table_query(a table) — before any edit. - Change as little as possible: a pinpoint edit, not a rewrite of the whole body from scratch, unless exactly that was asked for.
- Re-read after the write and only then confirm the success to the user.
MCP tools for reading
| Tool | Purpose |
|---|---|
resolve_folio_url |
A Folio link (/s/<space>, /s/<space>/p/<id>, /s/<space>/d/<dir>) → a particular page (id, path, parentPathForChildren). /s/<space> without /p/ = the home page of the space (index.md), NOT "the whole space". Call it first if the message contains a link |
list_spaces |
The spaces available to the user: slug, name, number of pages, role |
list_tree |
The full page tree of one space: id, title, kind, path, order |
read_page |
One page by id: metadata + the full markdown body (doc) or the scene (board) |
search_pages |
Full-text search, optionally within one space |
get_backlinks |
The links into the given page: the source page plus the line with the link (context) |
get_page_metadata |
One page's outline (headings with anchors), ^block ids, tags, properties (front matter) and outgoing links with their kind (page / asset / external / unresolved) |
list_unresolved_links |
Links in a space that point at no existing page (limit/offset, sorted by target) |
list_orphans |
Pages of a space nothing links to |
page_history |
The git commit history of a page: sha/author/date/message |
page_at_sha |
The content of a page at the given commit (a sha from page_history) |
folio_table_list |
The data tables of one space or of all available ones |
folio_table_schema |
The real columns, their types/options, the views, the number of rows |
folio_table_query |
The rows of a table with a filter/sort/search/limit |
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.
- today Changed · +3 lines 9f59e8a371ed
- 6d ago First seen · 129 lines · 30 tokens per session scan A b09e36860a48
Folio MCP is a skill published in the GitHub repository evergreen-it-dev/folio (69 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 2,035 once invoked, about $0.0001 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-issue-lifecycle
A GitHub Issue workflow for taking a code change from request to review, approval, testing, and closure. It can also keep a GitHub Project board—the task board attached to a repository—in sync.
do
Work a SpecWeave increment task by task - claim, implement inside the task's Files, test, commit, done with evidence - then verify and close. Use for "implement", "continue", "keep going".
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.
work
Pick up ready leaf yaks and implement them — dispatch subagents in isolated worktrees, then merge back to main.
sync
Sync SpecWeave increments with GitHub, Jira or Azure DevOps - push progress, pull or import issues, check token and health, run setup. Use for "sync", "push to GitHub", "import issues".