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 skills/fold-run/fold/update-docsnpx skills add fold-run/fold --skill update-docsgit 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.00073 | $0.00620 |
| Opus 5 | $0.00036 | $0.00310 |
| Sonnet 5 | $0.00015 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
update-docs 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update fold's docs from the working diff
Documentation drift is a merge-blocker in spirit here: README sections track code directly, and the schema drift test makes part of it literal. This skill turns "the diff changed behavior" into "the right doc surfaces changed with it".
1. Scope the drift
git diff --name-only HEAD # plus: git ls-files --others --exclude-standard
Map changed code to the surfaces that track it:
| Changed | Doc surface that must keep up |
|---|---|
gateway/router.go middleware order |
README "Request pipeline" |
config/config.go fields |
config/fold.config.schema.json (drift test), docs/configuration.md, docs/defaults.md, fold.config.example.json, and the README's config summary table if a whole section is added or removed |
| Minted error codes | README "Error codes" |
| New/changed endpoints, metrics | README "Operational endpoints" / "Observability", docs/operations.md |
| Auth, policy, EMA | docs/security-model.md, docs/configuration.md auth/policy sections |
Embedding API (gateway.New/Reload/Handler) |
docs/embedding.md, README "API stability" |
Deploy artifacts (Dockerfile, deploy/, compose) |
docs/deploy.md, README "Deploying" |
| Closing/widening a deliberate gap | README "Not implemented" |
| Architectural invariants (snapshot, sessions, pipeline) | CLAUDE.md |
Not doc-relevant: *_test.go-only changes, .claude/ changes, pure
refactors with no observable behavior change — say so and stop.
2. Delegate to the docs-sync agent
For anything beyond a one-line fix, launch the docs-sync subagent with: the list of changed files, a one-paragraph summary of the behavior change, and the specific surfaces from the table above it should audit. It verifies claims against code and edits the docs; relay its report.
Trivial single-surface fixes (one README line) may be done inline.
3. Verify
- Schema or example config touched →
go test ./config. CHANGELOG.mdis release-time only — never add entries there for unreleased work (that happens in/fold-releasestep 3).- Report: surfaces updated, surfaces checked-and-already-accurate, and anything deliberately deferred (e.g. changelog).
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 · 52 lines · 73 tokens per session scan A 2af788a36ae0
update-docs is a skill published in the GitHub repository fold-run/fold (1 stars, last pushed 2d ago), licensed Apache-2.0. It adds 73 tokens to every session and 620 once invoked, about $0.0004 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 skills, from other repositories
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
jwx-companion-bulk
Apply bulk operations across all jwx companion modules. Args.
sq-actions-dependabot
Reviews and merges Dependabot pull requests for GitHub Actions (the github-actions ecosystem) that bump uses: pins in .github/workflows/. Use for Dependabot githubactions PRs (branches like dependabot/githubactions/...), not go.mod or site/ Bun PRs.
readme-generate
從原始碼分析自動生成雙語 README。當使用者請求為專案建立 README、需要從程式碼庫生成 README.md（英文）和 README.zh.md（中文）、或希望為其函式庫/套件建立一致的多語言文件時使用。.
release-discord-post
Create a Discord-ready Neva release announcement from a GitHub release payload. Use for official Neva Discord release posts.