Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add fallow-rs/fallow-skills/plugin install 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/commands/fallow-rs/fallow-skills/impact-statusline)<a href="https://agentmods.dev/commands/fallow-rs/fallow-skills/impact-statusline"><img src="https://agentmods.dev/badge/commands/fallow-rs/fallow-skills/impact-statusline/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/commands/fallow-rs/fallow-skills/impact-statusline"><img src="https://agentmods.dev/badge/commands/fallow-rs/fallow-skills/impact-statusline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00013 | $0.00529 |
| Opus 5 | $0.00006 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
impact-statusline 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 3d 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
Fallow Impact statusline
Arguments: $ARGUMENTS
Manage Fallow's branded, compact Impact segment for Claude Code. Never enable Impact on the user's behalf.
Parse the request
- Action:
status,setup, orremove. Default tostatus. - Scope:
userorproject. Default touser. - Mode for setup:
replaceorcompose. projectmeans the private, gitignored.claude/settings.local.jsonin${CLAUDE_PROJECT_DIR}. Never edit the shared.claude/settings.json.
Command forms:
node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" inspect --scope user --root "${CLAUDE_PROJECT_DIR}"
node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" install --scope user --root "${CLAUDE_PROJECT_DIR}" --mode compose --confirm
node "${CLAUDE_PLUGIN_ROOT}/bin/fallow-impact-statusline.mjs" remove --scope user --root "${CLAUDE_PROJECT_DIR}" --confirm
Status
Run inspect and report:
- the exact preview;
- whether a statusline already exists;
- whether Fallow already manages it;
- the settings scope and path.
Do not modify files.
Setup
- Run
inspectfirst and show the exact preview. - If no statusline exists, use
replace. - If a command-based statusline exists and no mode was supplied, ask whether
to
composewith it orreplaceit. Recommendcompose. - If a non-command statusline exists and no mode was supplied, explain that it
cannot be composed and ask whether to
replaceit. - Only after that decision, run
installwith--mode <mode> --confirm. - Report the settings path and tell the user the statusline appears on the next Claude interaction.
If the preview says fallow impact off, tell the user they may run
fallow impact enable themselves. Do not run it.
Remove
Run remove --confirm and report the result. When the helper refuses because
the statusline changed after Fallow setup, tell the user and do not overwrite
their configuration by hand.
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.
- 3d ago Changed · -13 lines 010da563e573
- 10d ago First seen · 74 lines · 13 tokens per session scan A 5f56966e2254
impact-statusline is a command published in the GitHub repository fallow-rs/fallow-skills (121 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 529 once invoked, about $0.0001 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 commands, from other repositories
ultrathink
Command "ultrathink" from jellydn/my-ai-tools, covering usage, context, your role, process and output format.
simplify
Review recently modified code from three perspectives (Code Reuse, Code Quality, Efficiency) and apply all findings.
plannotator-annotate
Open interactive annotation UI for a markdown file.
plannotator-last
Annotate the last rendered assistant message.
amp-send
Send a message to another agent using the Agent Messaging Protocol.
amp-read
Read a specific message from your inbox.