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/fallow-rs/fallow/implementnpx skills add fallow-rs/fallow --skill implementgit clone --depth 1 https://github.com/fallow-rs/fallowWhat 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.00036 | $0.00266 |
| Opus 5 | $0.00018 | $0.00133 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
implement 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.
What it actually says
Implement
Deliver the requested change through the native Fallow lifecycle.
- Read
AGENTS.md,docs/README.md, anddocs/development/task-context-map.md. - Inspect the live branch, worktree, open pull requests, and
origin/main. - Write the acceptance criteria and verification plan to the gitignored
.plans/<task>.md. - For changes with user-facing design decisions, run
panel-reviewbefore editing. - Create an implementation branch and ready pull request before tracked edits.
- Implement in pipeline order and keep generated contracts, public docs, and companion repositories synchronized.
- Run every applicable gate from
docs/development/quality-gates.md. - Run the reviewer set selected by
docs/development/review-routing.md. Resolve every block. - Update the pull request with current verification evidence.
Use apply_patch for edits. Preserve unrelated work. Never create process
artifacts under committed docs/. Prefer durable knowledge in indexed docs and
keep this skill procedural.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 28 lines · 36 tokens per session scan A 01185518aa7e
implement is a skill published in the GitHub repository fallow-rs/fallow (4,429 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 266 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-30.
Other skills, from other repositories
Biome
Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.
eslint-docs
ESLint 10.x — flat config, rules, plugins, formatters, parsers, CLI, Node.js API, custom rules, migration.
biome-code-review
Use this skill only when asked to review completed Biome changes in a PR, branch, commit range, diff, or working tree. Perform a read-only static review and report findings without editing files or running project code. Do not use for triage, reproduction, or implementation.
doc-comments
Use this skill whenever writing or editing Rust //, ///, or //! comments in Biome, including comments added incidentally and end-user rustdoc inside lint/assist declarations. For lint/assist rustdoc, also load lint-rule-development for content requirements. Do not use for formatter handling of comments in user code.
type-inference
Use this skill when working on Biome's Salsa-backed JavaScript and TypeScript inference, including type-aware lint rules, raw collection or inferred representations, analyzer requests, tracked queries, import or cycle resolution, profiling, and Salsa invalidation tests. Do not use for standalone CSS/HTML module-graph…
eslint-migrate-options
Use this skill when biome migrate eslint must preserve configurable ESLint rule options through source-option models, Biome conversions, typed rule variants, and migration fixtures. Do not use for generated severity-only mapping or general rule-option design.