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 VKirill/claude-lane-stack --skill orchestrator-lanesgit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/orchestrator-lanes)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/orchestrator-lanes"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/orchestrator-lanes/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/skills/vkirill/claude-lane-stack/orchestrator-lanes"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/orchestrator-lanes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 62 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 62 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00000 | $0.05276 |
| Opus 5 | $0.00000 | $0.02638 |
| Sonnet 5 | $0.00000 | $0.01055 |
| Haiku 4.5 | $0.00000 | $0.00528 |
Grade A, and why
orchestrator-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 11d 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator lanes — solo operator
Info (print and stop)
If $ARGUMENTS is info, or the user says info / справка / как запускать this skill:
print the block below verbatim (Russian), then stop. Do not score. Do not run-init.
orchestrator-lanes — раны (только сессия dev-orchestrator)
Когда
- Человек сказал «делай / реализуй / в работу / запускай ран».
- До этого — project-life, план в .agents/plans/. Ран не открывать.
Как открыть шпаргалку
- /lane-stack:orchestrator-lanes info
- каталог всех процессов: /lane-stack:info
Старт рана
1) cwd = проект. Сессия = dev-orchestrator.
2) Score один раз (0–2 micro … 11+ спроси).
3) run-init → заполнить PLAN/SPEC/tasks по lane-contract.
4) run-validate --phase pre-dispatch.
5) Один Agent(run-supervisor) на ран.
6) lane из adoc (.agents/routing.profile.yaml), не хардкод kimi.
UI
- Нужны полные docs/DESIGN.md и apps/<app>/docs/DESIGN.md.
- Нет файла → сначала design-lead, потом run-init.
- Task read_first: оба DESIGN.md. Не в owns_paths, если исход не токены.
Нельзя
- run-init на фразе «планируем / не запускай»
- Claude Plan mode / ~/.claude/plans/
- второй run-supervisor на тот же ран
- просить человека мержить main
Load: karpathy-guidelines, lane-contract, project-life, resume-project, project-design, ui-ux-pro-max.
Docs: FILE-CONTRACT.md, ROUTING.md, SOLO-ORCHESTRATION.md,
PLATFORM-CAPABILITIES.md (Claude Code + Codex features we use),
docs/decisions/ADR-codex-effort.md under the lane-stack / ~/.agents/docs/.
You are the only person who merges to main. Human never merges.
Planning vs run
If the user is in a planning session (project-life: «планируем /
не запускай / спланируй / обсудим / пока план») or has not said
«делай / реализуй / в работу / запускай ран»:
- Do not announce score,
run-init, or dispatch writers. - Follow project-life → Planning session. Write
.agents/plans/only. - New app or service talk («архитектор / новое приложение / новый сервис»):
load app-architect. Same draft plan, living
artifacts/. Still no run. - Claude Code Plan mode is not this. Do not write
~/.claude/plans/. If the host is in Plan mode, tell the user to switch to default.
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.
- 11d ago First seen · 429 lines · 0 tokens per session scan A b5cfa4ee292a
orchestrator-lanes is a skill published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,276 tokens. 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
swarm-plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
loop
Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…
issue-ingest
Full execution protocol for MODE: ISSUEINGEST -- GitHub issue intake, localization, spec generation, and transition to the full fix workflow.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
phase-wrap
Claude Code adapter for MODE: PHASE-WRAP. Delegates to the canonical opencode-swarm phase boundary protocol.
production-scheduling
You are a senior production scheduler at a discrete and batch manufacturing facility operating 3–8 production lines with 50–300 direct-labor headcount per shift. You manage job sequencing, line balancing, changeover optimization, and disruption response across work centers that include machining, assembly, finishing…