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 team-routesgit 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/team-routes)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/team-routes"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/team-routes/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/team-routes"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/team-routes.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.00055 | $0.01103 |
| Opus 5.5 | $0.00022 | $0.00441 |
| Sonnet 5.5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
team-routes 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 13d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team routes
The operator states a goal, not a staffing plan. You decide who works on it. A page built without its SEO, UX and copy inputs comes back as placeholders and gets redone; a one-line fix sent through four specialists burns an hour of expensive models. Pick the smallest team that produces the artifact the operator actually needs.
1. Name the deliverable
Before Score/Decompose, write one line for yourself:
deliverable: <artifact> · surface: <page/app/feature> · slug: <kebab-slug>.
The deliverable is what the operator will open at the end: a gray prototype, a branded mockup, shipped code, an article, an audit report, an answer with sources. Ambiguous wording («сделай страницу») means the cheapest deliverable that still moves the goal (prototype before code) unless the operator said «в код», «на сайт», «задеплой» or the page already exists in code.
2. Pick or compose a route
Start from the closest recipe in references/recipes.md.
Drop a step when its output already exists on disk and is not stale (for
example .agents/copy/pages/<slug>.md is there, so copy only fills gaps). Add a step
when the goal needs a role the recipe lacks. No recipe fits → compose a route
from the role cards in references/roles.md: each step's
inputs must be outputs of earlier steps or existing files.
Run steps in parallel when neither reads the other's output. Run them in order when one decides what the next one writes about (SEO intent before copy).
Not every request needs a route. Go straight to the existing Loop when the goal is product code with no new user-facing text or layout (bug, refactor, API, infra), or a question you can answer from the repo.
3. Announce and start
Post one Russian line, then start the first step in the same turn. Do not wait for approval: the operator asked for the result, and the line exists so they can redirect you.
Маршрут: seo ∥ design-lead (UX) → copy-lead → design-lead (прототип) → design-lead (аудит). Начинаю.
What ships with it
2 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.
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.
- 13d ago Changed ba90b12fdded
- 15d ago First seen · 103 lines · 55 tokens per session scan A 59f8c529c139
team-routes is a skill published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,103 once invoked, about $0.0002 per session on Opus 5.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-10-02.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
self-assessment
Interactive skill assessment with personalized learning path generation.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.