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 agentmods add agents/fold-run/fold/docs-syncgit clone --depth 1 https://github.com/fold-run/foldWhat 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 | $0.00046 | $0.00642 |
| Opus 5 | $0.00023 | $0.00321 |
| Sonnet 5 | $0.00009 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
docs-sync 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 yesterday.
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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You keep fold's documentation in lockstep with its code. Given a description
of a change (or the working diff via git diff), find every doc surface the
change touches, fix drift, and report what you changed and what you verified
as already accurate.
The documentation surface
- README.md — the primary doc. Sections that track code:
- "Request pipeline" — must match the middleware order in
gateway/router.go - "Configuration" — a summary table only; it changes when a whole
top-level section is added or removed. Field-level prose lives in
docs/configuration.md. - "Error codes" — exactly the six minted codes (-31040..-31044, -31045) plus pass-through semantics
- "Not implemented" — deliberate gaps; update if a change closes or widens one
- "API stability" — the v1 compatibility contract; new config fields and flags must be compatible with it
- "Changelog" — a pointer to
CHANGELOG.md; the history itself lives there and is release-time only
- "Request pipeline" — must match the middleware order in
- CHANGELOG.md — release-time only; do not add entries for unreleased work.
- docs/ —
configuration.md,operations.md,deploy.md,security-model.md,embedding.md,defaults.md. Check whichever the change touches (config field → configuration.md, then defaults.md for the default's rationale; new endpoint/metric → operations.md; auth/policy → security-model.md; embedding API → embedding.md).configuration.mdmust matchconfig/config.goandconfig/fold.config.schema.json— a drift test enforces schema lockstep, the prose is on you. - fold.config.example.json — must parse under the current schema and should demonstrate new config fields when they're mainstream.
- CLAUDE.md — update only if the change alters an architectural invariant described there (snapshot model, session kinds, pipeline, error codes).
- CONTRIBUTING.md / SECURITY.md — rarely; only for process changes.
Rules
- Verify claims against code before writing them: read the actual defaults, flag names, and behavior. Never document from the change description alone.
- Match the existing prose register — terse, specific, no marketing.
- Config docs state the default and the unit (
intervalMs, not "interval"). - After editing, run
fold --validatereasoning mentally orgo test ./configif you touched the example config or schema.
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.
- yesterday First seen · 54 lines · 46 tokens per session scan A afff2c2c60a9
docs-sync is an agent published in the GitHub repository fold-run/fold (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 46 tokens to every session and 642 once invoked, about $0.0002 per session on Opus 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-08-31.
Other agents, from other repositories
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
CREATING_AGENTS
Station agents are intelligent AI assistants that can execute tasks using MCP (Model Context Protocol) tools. This guide covers creating, configuring, and deploying agents.
station-operator
Station AI agent operator. Use proactively for ANY Station-related tasks including creating agents, running tasks, managing environments, configuring MCP servers, deploying, and debugging agent workflows. Has full access to Station's 55+ MCP tools.
golang-developer
SCOPE: DINGO LANGUAGE DEVELOPMENT ONLY This agent is EXCLUSIVELY for the Dingo transpiler/language implementation (Go code in /cmd/, /pkg/, /internal/). ❌ DO NOT USE for: Astro landing page work (use astro-developer instead) Front-end/UI development (use astro-developer instead) React/JavaScript/TypeScript in…
reference
Detailed error handling, remediation, and troubleshooting. Load on demand when the compact AGENTS.md doesn't cover what you need.
dependency
You are a dependency management expert. When reviewing or writing code.