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 resume-projectgit 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/resume-project)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/resume-project"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/resume-project/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/resume-project"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/resume-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 29 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.00087 | $0.00662 |
| Opus 5.5 | $0.00035 | $0.00265 |
| Sonnet 5.5 | $0.00017 | $0.00132 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
resume-project 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 21d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume project
Default: run. Info card only if $ARGUMENTS is exactly info.
Inside a Lane Pilot chat (
LANE_PILOT_AGENT_TYPEset / toolslane_pilot_*present) cold start is not the CLI: read.agents/PROGRESS.md,.agents/plans/ROADMAP.mdand the open counts in.agents/todos/INDEX.md, then take the run state from the Lane Pilot tools (lane_pilot_workspace_status,lane_pilot_gate_report) and prior decisions from hub memory (lane-memory search,lane_pilot_memory_context). Answer in Russian: Now / Blocked / Next. Day policy there: writer → plan and code critique → acceptance → merge, all by Lane Pilot. HANDOFF/BOARD,next_actandresume-projectbelow are the terminal harness.
Procedure (terminal)
- Run (prefer compact day brief):
export PATH="$HOME/.agents/bin:$PATH"
resume-project "$(pwd)" --compact
This regenerates .agents/HANDOFF.json + HANDOFF.md and prints them first.
-
Synthesize in RU (short) from HANDOFF, not from raw BOARD dump:
- Now
- Blocked +
next_act(e.g.fix_contract— do not re-dispatch writer) - Next typed acts only
- Profile:
main_write+ workspace mode
-
Day policy reminder (terminal): write → L1 verify → accept → merge. No daytime LLM review; night-shift owns review/fix.
-
If stalled tasks: re-dispatch or mark blocked — do not ignore. For schema v2, never mutate task YAML after first start.
-
Do not dump full files into chat — point paths. Full archaeology only if needed:
resume-project . --full
Optional
lane-memory searchfor prior decisions (hub memory)night-auditif user asks overnight reviewhandoff-write .alone to refresh without full resume
Boundaries
- Merging is yours or the controller's, so do not ask the human to merge branches.
- The PM plans and verifies; coding goes to a writer lane.
- When
next_actisfix_contract(missing check.py, lane mismatch) repair the contract first: a blind retry fails the same way.
What ships with it
1 file 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.
- 21d ago Changed · -29 lines · +20 tokens per session 48eb65bb1071
- 1mo ago Changed · +2 lines · +15 tokens per session a0daba428efc
- 1mo ago First seen · 81 lines · 52 tokens per session scan A 990c40614ad7
resume-project is a skill published in the GitHub repository VKirill/claude-lane-stack (124 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 662 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
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.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
dev-docs
A documentation process for recording project progress, architecture decisions, development handovers, and user-visible releases. It organises these records into navigation, dated details, architecture notes, and a changelog.
ui-sync
A workflow for keeping the user interface's task status in sync when adding new features. It uses task.json as the source of truth and updates runtime progress during building and review.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
sprint-end
Use when the user wants to ship a sprint's work to main via PR.