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 skills/melodic-software/claude-code-plugins/lanesnpx skills add melodic-software/claude-code-plugins --skill lanesgit clone --depth 1 https://github.com/melodic-software/claude-code-pluginsWhat 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.00195 | $0.05093 |
| Opus 5 | $0.00097 | $0.02547 |
| Sonnet 5 | $0.00039 | $0.01019 |
| Haiku 4.5 | $0.00019 | $0.00509 |
Grade A, and why
lanes 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-computed context
claude CLI: !claude --version 2>/dev/null || echo "MISSING (required)"
jq: !command -v jq >/dev/null 2>&1 && echo "present" || echo "MISSING (required)"
Repo root: !git rev-parse --show-toplevel 2>/dev/null || echo "unknown (pass --repo)"
Lane config: !bash "${CLAUDE_PLUGIN_ROOT}/skills/lanes/scripts/probe-lane-config.sh" 2>/dev/null || echo "unknown"
Variables
Arguments: $ARGUMENTS
Purpose
Running N loop lanes on a machine means a daily ritual: for each lane, cancel its
loop, clear, and re-paste its canonical prompt. This skill collapses that to one
command. start/restart pull the repo and refresh the plugin marketplace once,
then launch each configured lane as a named background session seeded from the
lane's canonical prompt file, mirroring that lane's model/effort onto the launch.
status/stop read and manage those sessions through the CLI's own
background-session surface.
Owns only its own lanes. stop/restart act on a session only when its
name is a lane in the resolved config, a hand-started session (e.g. an interactive
work window, or an unrelated PR Babysit) is never stopped by this skill.
A relaunch is the only context reset a loop lane gets
/loop re-invokes its prompt in the same session (it self-paces via
ScheduleWakeup), so a lane's context carries forward across every cycle, subagent
return, and operator turn, the loop never starts a fresh one. A running loop
cannot reset its own context on demand: a built-in like /clear issued from a
loop re-run reaches the model as plain text, not an executed command, so the model
cannot /clear itself. Any "restart the loop when context passes ~N%" discipline is
therefore an admonition with no in-session enforcement, the lane has no reliable way
to measure its own context usage and no way to act on the threshold if it could.
The context change that does happen automatically in-session is Claude Code's auto-compaction: when the conversation nears the model's input limit, older history is summarized in place to free space. That is not a reset, the session continues on a lossy summary of what came before, not a fresh context, so a lane that runs long enough will lose earlier context to compaction well before any operator relaunch, not keep every turn until then.
What ships with it
14 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.
- context/config.md 5.4 KB
- context/refresh.md 9.0 KB
- context/restart-consumer.md 14 KB
- evals/evals.json 6.1 KB
- scripts/lane-launcher.sh 44 KB runs code
- scripts/lane-launcher.test.sh 57 KB runs code
- scripts/machine-behavior.sh 9.2 KB runs code
- scripts/machine-behavior.test.sh 8.7 KB runs code
- scripts/probe-lane-config.sh 2.7 KB runs code
- scripts/probe-lane-config.test.sh 8.0 KB runs code
- scripts/restart-consumer.sh 55 KB runs code
- scripts/restart-consumer.test.sh 44 KB runs code
- scripts/telemetry-upsert.sh 23 KB runs code
- scripts/telemetry-upsert.test.sh 31 KB runs code
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 First seen · 324 lines · 195 tokens per session scan A 9bf516301fb8
lanes is a skill published in the GitHub repository melodic-software/claude-code-plugins (12 stars, last pushed 2d ago), licensed MIT. It adds 195 tokens to every session and 5,093 once invoked, about $0.0010 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 skills, from other repositories
deep-research
Conducts iterative deep research on any topic using web search, progressive exploration, and structured synthesis. Use when asked for comprehensive research, deep investigation, thorough analysis, or multi-source exploration of any topic. Triggers: research, investigate, deep dive, comprehensive analysis, explore…
error-ux
Principles and patterns for writing error messages that help users recover. Use when auditing, writing, or improving error messages in code. Triggers: error messages, user experience, error handling, exception messages, validation errors.
adversarial-patterns
Library of realistic adversarial attack vectors and anti-patterns to avoid. Contains examples of valid attacks and subtle gaming patterns to reject.
documentation-testing
Provides heuristics for identifying incomplete or broken documentation. Use when validating README setup instructions, testing onboarding flows, or auditing documentation quality. Triggers: docs, readme, onboarding, setup validation, documentation audit.
adversarial-analysis
Analyze code to identify explicit contracts, implicit usage patterns, and realistic boundary conditions. Contains concrete formulas for calculating input realism limits. Use before generating adversarial tests.
propagate-then-search
For constraint problems: eliminate impossibilities before guessing, reduce search space through inference, fail fast on contradictions.