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 fallow-rs/fallow-skills --skill fallowgit clone --depth 1 https://github.com/fallow-rs/fallow-skillsWrote 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-skills/fallow)<a href="https://agentmods.dev/skills/fallow-rs/fallow-skills/fallow"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow-skills/fallow.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk 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.00114 | $0.12728 |
| Opus 5 | $0.00057 | $0.06364 |
| Sonnet 5 | $0.00023 | $0.02546 |
| Haiku 4.5 | $0.00011 | $0.01273 |
Grade C, and why
fallow scanned grade C with 2 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 2d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
| `health` | Function complexity analysis (also covers component templates as synthetic `<template>` findings: Angular external `.html` files via `templateUrl` AND inline `@Component({ template: \`...\` })` literals, plu Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
| `boundary-violation` | `--boundary-violations` | - | `// fallow-ignore-next-line boundary-violation` | Imports crossing architecture zone boundaries. Presets: `layered`, `hexagonal`, `feature-sliced`, `bulletproof`; `a How it starts
The opening of the file, as written. The whole thing — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fallow: codebase intelligence for TypeScript and JavaScript
Codebase intelligence for TypeScript and JavaScript. The static layer analyzes code and styles and reports quality, changed-code risk, cleanup opportunities, circular dependencies, code duplication, complexity hotspots, architecture boundary violations, design-system styling drift, feature flag patterns, and opt-in security candidates. Runtime coverage merges production execution data into the same fallow health report for hot-path review, cold-path deletion confidence, and stale-flag evidence, with a single local capture available by default and continuous/cloud runtime monitoring available as an optional mode. Broad framework plugin coverage, zero configuration, sub-second static analysis.
When to Use
- Find cleanup opportunities: unused files, exports, types, members, dependencies, or stale flags.
- Detect code duplication, circular dependencies, architecture boundary issues, and complexity hotspots.
- Find functions that may implement the same intent despite different names, syntax, or control flow (
fallow similar-code). - Check styling consistency, CSS dead surface, and design-token drift.
- Audit changed code before a commit, PR, release, or refactor.
- Set up CI quality gates, duplication thresholds, and regression baselines.
- Auto-fix supported unused exports and dependencies after
--dry-run. - Investigate why a specific export, dependency, file, or issue type was reported.
- Surface local security candidates for an agent to verify (
fallow security). - Find untested but runtime-reachable code (
fallow health --coverage-gaps). - Rank complexity hotspots, owners, and refactoring targets (
fallow health --hotspots --ownership --targets). - Review what fallow has surfaced over time (
fallow impact). - Confirm exact TypeScript symbol use, affected tests, API leaks, or public type coupling when syntactic evidence is insufficient (
--type-aware).
When NOT to Use
- Runtime error analysis or debugging
- Type checking (use
tscfor that). Type-aware fallow consumes checker evidence for project-wide analysis but does not report compiler diagnostics. - Linting style or formatting issues (use ESLint, Biome, Prettier)
- Verified security vulnerability scanning or SAST.
fallow securitysurfaces local, deterministic security candidates for a downstream agent to verify; it does not prove exploitability. Use Snyk, CodeQL, or Semgrep for verified scanning, and an SCA tool for dependency CVEs. - Bundle size analysis
- Projects that are not JavaScript or TypeScript
What ships with it
7 files 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.
- 2d ago Changed · +1 lines 6f43bd8e29d7
- 8d ago First seen · 498 lines · 114 tokens per session scan C 88fbecfaef1d
fallow is a skill published in the GitHub repository fallow-rs/fallow-skills (119 stars, last pushed today), licensed MIT. It adds 114 tokens to every session and 12,728 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (hidden instructions, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
code-review
Review the diff since a fixed point along two axes — Conventions (does the code follow this repo's coding standards and Tidy First practices?) and Intent (does the change do what it claims to do?). Runs both reviews in parallel sub-agents and reports them side by side. Use when you want to review a branch, a PR…
slop
Remove AI-generated code slop from git diffs to maintain code quality.
pr-review
Fix PR review comments by implementing requested changes.
code-quality-review
Run an extremely strict maintainability and structural code quality review — flags abstraction issues, spaghetti growth, and boundary leaks.
code-reviewer
Review code for quality, security, and best practices — read-only analysis.
ai-slop-remover
Remove AI-generated code patterns that don't match codebase style.