Fallow is a command-line static-analysis tool that builds a dependency graph of TypeScript and JavaScript code to identify unused code, duplication, circular dependencies, complexity hotspots, boundary violations, and styling drift. It is for developers reviewing codebases and verifying changes, with catalogue entries that add agent, editor, and workflow integrations.
Borrowing it
Nothing to install: this file belongs to fallow-rs/fallow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fallow-rs/fallow/main/.agents/skills/implement/SKILL.mdgit clone --depth 1 https://github.com/fallow-rs/fallowWrote 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/fallow-rs/fallow/implement)<a href="https://agentmods.dev/skills/fallow-rs/fallow/implement"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/implement/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/fallow-rs/fallow/implement"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00474 |
| Opus 5.5 | $0.00014 | $0.00190 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00004 | $0.00047 |
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 16d 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.
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. - Resolve open decisions before editing. Sort each open question:
- fact: the code, docs or history hold the answer; look it up;
- observable: a run shows the answer; probe a fresh build on a public
fixture with
--format json --quiet. When the change models another tool (pnpm, npm, Bun, tsc), probe that tool too: the oldest supported version, the installed one and the latest major. Narrow a version boundary down to the patch release; - decision: scope, naming, contract or trade-off; ask the maintainer in one round, with a recommended answer for each question. Record the answers in the plan. Skip this step when no decision is open.
- 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. Follow the test evidence rules in
docs/development/quality-gates.md. For a bug, get a command that fails before you change code; after a restart, suspect the.fallow/cache first. - 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 and the proof level of each claim.
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.
- 16d ago Changed · +3 lines ef865c596471
- 24d ago Changed · +10 lines 6e68e61a9477
- 1mo ago Changed 1cea440acbee
- 1mo ago First seen · 28 lines · 36 tokens per session scan A 01185518aa7e
implement is a skill published in the GitHub repository fallow-rs/fallow (5,157 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 474 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
biome
Biome - Fast all-in-one toolchain for web projects (linter + formatter in Rust, 100x faster than ESLint).
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…
poly-lint-and-format
Running poly lint / poly fmt — --fix, --format pretty|json|toon, --exclude, --config, exit codes, inline suppression, and the check → read-json → fix → re-check loop.
dispatcher
Use this skill when running a Taniwha build from the main Claude Code session. The skill turns the main session into a thin, mechanical executor that follows instructions from ephemeral orchestrator subagents. Trigger this whenever the user wants to start a Taniwha build, resume an interrupted one, or work on a…
poly-tiers-and-scope
Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs).
poly-overview
What poly is — the native, tree-sitter, native-toolchain, quality, and built-in-rule-pack tiers, language coverage, and when to reach for it.