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-tablesgit 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-tables)<a href="https://agentmods.dev/skills/evergreen-it-dev/folio/folio-tables"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-tables/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-tables"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-tables.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.00044 | $0.02294 |
| Opus 5.5 | $0.00018 | $0.00918 |
| Sonnet 5.5 | $0.00009 | $0.00459 |
| Haiku 4.5 | $0.00004 | $0.00229 |
Grade A, and why
Folio Tables 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Folio data tables (kind: table)
A separate kind of page next to the document and the board: a grid with a
schema of columns, rows and tab views, stored as one .table.md file in
git. The normative specification is docs/spec-tables.md; this skill is an
operational digest for the folio_table_* tools from server/mcp.ts.
This is not the same as an extended markdown table inside a document
(colspan/rowspan/backgrounds — the folio-content skill). A data table is a
page of its own, with its own schema of types and its own API.
The iron rule: the schema first
Before any reading or writing of rows — always folio_table_schema as the
first call. The ids of columns, the types and the allowed values of
select/status cannot be guessed from the name of a column or from
experience with a "similar" table — every table has its own real schema.
The workflow
folio_table_list(optionally withspace) — find the table you need, if itsidis not known yet.folio_table_schema— the real columns (id/name/type/options), the views, the number of rows.- Reading rows —
folio_table_querywithfilter/sort/q/view/limit/offset,format: 'markdown'for a concise look or'json'for exact values. - Writing —
folio_table_insert/folio_table_update/folio_table_delete/folio_table_add_column, in AGENT mode only. - After a write — re-read (
folio_table_query/folio_table_schema) and only then confirm the result to the user.
Column types (v1)
| Type | What it is | The value in the API |
|---|---|---|
text |
single-line text | string |
longtext |
multi-line text | string (with line breaks) |
number |
a number, with precision (0-6 digits) |
number |
date |
a date, optionally with time (time: true) |
an ISO string |
checkbox |
yes/no | boolean |
select |
one (or, with multiple: true, several) values from the options list |
string or string[] |
status |
the same as select, but semantically for the state of a process | string |
user |
a member of the space (@handle), multiple — several |
string or string[] |
link |
a URL (or a relative path to a Folio page) with an optional caption | 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 · 191 lines · 44 tokens per session scan A 874447776382
Folio Tables is a skill published in the GitHub repository evergreen-it-dev/folio (69 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 2,294 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-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".