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 commands/jszmajda/lid/arrow-maintenancegit clone --depth 1 https://github.com/jszmajda/lidWrote 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/jszmajda/lid/arrow-maintenance)<a href="https://agentmods.dev/commands/jszmajda/lid/arrow-maintenance"><img src="https://agentmods.dev/badge/commands/jszmajda/lid/arrow-maintenance.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.00185 |
| Opus 5 | $0.00030 | $0.00093 |
| Sonnet 5 | $0.00012 | $0.00037 |
| Haiku 4.5 | $0.00006 | $0.00018 |
Grade A, and why
arrow-maintenance 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 5d 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
Invoke the arrow-maintenance skill in command mode. The skill dispatches on project state: audits and updates an existing overlay, bootstraps the overlay from existing LID docs if absent, or redirects the user to /map-codebase (for brownfield) or /linked-intent-dev (for greenfield — invoke with a description of what to build; the workflow bootstraps LID as part of Phase 1) when LID is not installed. See plugins/arrow-maintenance/skills/arrow-maintenance/SKILL.md for the full behavior.
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.
- 5d ago First seen · 7 lines · 59 tokens per session scan A 1576c785d94d
arrow-maintenance is a command published in the GitHub repository jszmajda/lid (100 stars, last pushed 23d ago), licensed MIT. It adds 59 tokens to every session and 185 once invoked, about $0.0003 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
pkg
Use pkg to search packages, verify installs, and scan dependency files.
weave
Use weave to create, run, and replay API workflows.
task
Command "task" from d4rkNinja/infynon-cli, covering task, when to use, basic usage, common commands and important options.
trace
Use trace to save repo context, implementation notes, and package/file/branch memory.
workspace
Use workspace to manage project locations, folder aliases, model slots, and the agent root.
coding
Use coding to launch coding agents or open the workspace/task TUI.