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-basesgit 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-bases)<a href="https://agentmods.dev/skills/evergreen-it-dev/folio/folio-bases"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-bases/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-bases"><img src="https://agentmods.dev/badge/skills/evergreen-it-dev/folio/folio-bases.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.01049 |
| Opus 5.5 | $0.00016 | $0.00420 |
| Sonnet 5.5 | $0.00008 | $0.00210 |
| Haiku 4.5 | $0.00004 | $0.00105 |
Grade A, and why
Folio Bases 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bases (kind: base)
A base is a .base file (Obsidian's YAML format): a saved query over the
pages of a space, not a store of its own. Its rows are pages (only those the
reader may open), its columns are their properties (front matter), file fields
and formulas. To change a value in a base you change that page's property
(set_page_properties with merge: true), not the base.
Tools
| Tool | What it does |
|---|---|
read_page (base id) |
The YAML of the base |
query_base |
The rows of one view: values by column, groups, summaries (view, limit, offset) |
list_properties |
The property keys used in a space with their types and sample values — look here before writing a filter |
list_tags |
The tags of a space, for file.hasTag(...) filters |
save_base |
Create a base (path, e.g. "projects/tasks.base") or replace one (id + etag) from the whole yaml |
set_page_properties |
Change the property a base shows, on the page itself |
The file
filters: # which pages are rows (optional): and / or / not of expressions
and:
- file.inFolder("projects")
- file.hasTag("task")
- 'status != "done"'
formulas: # computed columns, used as formula.<name>
overdue: 'due < today()'
views:
- type: table # table, cards or list
name: Open tasks
order: # the columns, in order
- file.name
- owner
- status
- due
- formula.overdue
sort:
- property: due
direction: ASC
groupBy:
property: owner
direction: ASC
limit: 100
- type: cards
name: By owner
order: [file.name, owner]
- Properties: a bare name or
note.<key>is a front matter key (status,note.status);file.name,file.folder,file.path,file.ext,file.tags,file.mtime,file.ctime,file.size,file.links,file.backlinksare file fields;formula.<name>is a formula. - Expressions (filters and formulas): comparisons
== != < > <= >=,&&,||,!, arithmetic, strings in double quotes (quote the whole YAML line with single quotes when it contains"or:). Functions:file.hasTag("a"),file.inFolder("dir"),file.hasLink("Page"),file.hasProperty("key"),today(),now(),date("2026-10-01"),if(cond, a, b),list(x),x.isEmpty(),x.contains("y"),number(x),min(),max(). - A view's own
filtersnarrow the base's top-levelfiltersfurther. summariesper view map a column to a built-in summary —Sum,Average,Min,Max,Median,Range,Earliest,Latest,Checked,Unchecked,Empty,Filled,Unique— or to a key of the base's own top-levelsummaries(summaries: { estimate: Sum }).
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 First seen · 87 lines · 41 tokens per session scan A 53575fa8a248
Folio Bases is a skill published in the GitHub repository evergreen-it-dev/folio (71 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 1,049 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-17.
Other skills, from other repositories
youtube-fetcher
Retrieve YouTube transcripts and subtitles, summarize or analyze what was said, or save an Obsidian-ready Markdown knowledge-base note with captions, creator metadata, chapters, language, and source provenance. Use for a YouTube URL or video ID when the request needs spoken content or an archival note. A bare YouTube…
obsidian-docs
Create comprehensive technical documentation following Obsidian conventions with bidirectional linking, proper folder structure, templates, and developer-focused content. Use when creating documentation, READMEs, wikis, knowledge bases, ADRs, runbooks, or any technical writing. Triggers on: documentation, docs…
second-brain-ingest
Process raw source documents into wiki pages. Use when the user adds files to raw/ and wants them ingested, says "process this source", "ingest this article", "I added something to raw/", or wants to incorporate new material into their knowledge base.
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
install-by2kb
Install, configure, update, or diagnose the by2kb CLI for this Hermes plugin. Preserve existing configuration and keep Hermes-managed plugin code separate from CLI upgrades.