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.
git 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/plugins/fallow-rs/fallow-skills/fallow)<a href="https://agentmods.dev/plugins/fallow-rs/fallow-skills/fallow"><img src="https://agentmods.dev/badge/plugins/fallow-rs/fallow-skills/fallow/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/plugins/fallow-rs/fallow-skills/fallow"><img src="https://agentmods.dev/badge/plugins/fallow-rs/fallow-skills/fallow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fallow 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 today.
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
{
"name": "fallow",
"displayName": "Fallow Code Analysis",
"version": "1.4.26",
"description": "Local-first codebase intelligence and Impact summaries for TypeScript and JavaScript using fallow",
"author": {
"name": "Bart Waardenburg",
"email": "[email protected]"
},
"homepage": "https://fallow.tools",
"repository": "https://github.com/fallow-rs/fallow-skills",
"license": "MIT",
"keywords": [
"fallow",
"dead-code",
"duplication",
"complexity",
"static-analysis",
"javascript",
"typescript"
]
}
What it installs
The manifest is a name and a version. 4 skills, 1 command, 1 hook travel with it, and installing the plugin installs all of them — 487 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- today Changed 459bf4b65824
- 2d ago Changed 29737e3ba353
- 3d ago Changed 17d86e1007fa
- 4d ago Changed 3c14ed135358
- 6d ago Changed 82f85813844b
- 7d ago Changed 83c92dd7d347
- 8d ago Changed 642abaabfde1
- 9d ago Changed d126edeb5e11
- 10d ago Changed 6383b946df08
- 11d ago First seen · 23 lines scan A e9332210290b
fallow is a plugin published in the GitHub repository fallow-rs/fallow-skills (131 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
codeeraser
CodeEraser passive guard + erase skill: a winnowing clone index behind a per-project daemon intercepts T1/T2 duplicate writes at PreToolUse (with the tombstone and flow legs judged in the core), records at PostToolUse whether an asked write ran (settle), audits net LOC + touched duplicates at Stop, and reports health…
datadog
Access Datadog logs, metrics, monitors, dashboards, SLOs, events, traces, and incidents.
agent-alchemy-dev-tools
Agent Alchemy Dev Tools — dev utilities, debugging, and workflow enhancements.
incident-response
Production incident management, triage workflows, and automated incident resolution.
apple-craft
A collection of skills for Apple-platform development, including implementation, debugging, code review, long-running projects, App Store delivery, Xcode integration, and Pencil design work. Xcode is Apple's tool for building its apps, and the App Store is Apple's software marketplace.
debugging
Systematic debugging skills: root cause tracing, defense-in-depth validation, verification before completion.