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.00067 | $0.00671 |
| Opus 5 | $0.00034 | $0.00336 |
| Sonnet 5 | $0.00013 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
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 4d 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 — 83 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.
MUST
- 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: 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
MAY
mcp__agentmemory__memory_smart_searchfor prior decisionsnight-auditif user asks overnight reviewhandoff-write .alone to refresh without full resume
NEVER
- Ask human to merge branches
- Start coding as PM
- Blind retry when
next_actisfix_contract(missing check.py, lane mismatch)
Info (only when $ARGUMENTS is info)
Print the block below verbatim (Russian), then stop. Do not run resume-project.
resume-project — холодный старт («где мы»)
Когда
- Новая сессия оркестратора на живом репо.
- «где мы / продолж / resume / handoff».
- Не для туду и не для нового онбординга.
Как открыть шпаргалку
- /lane-stack:resume-project info
- каталог: /lane-stack:info
Запуск
- /lane-stack:resume-project
- /resume-project
- CLI: ~/.agents/bin/resume-project "$(pwd)" --compact
Что ответить (из HANDOFF, коротко по-русски)
- Now
- Blocked + next_act (fix_contract → не респавнить writer)
- Next — только типизированные акты
- Profile: main_write + workspace
Нельзя
- просить человека мержить
- кодить как PM
- слепой retry при next_act=fix_contract
- вываливать сырой BOARD в чат
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.
- 4d ago Changed · +2 lines · +15 tokens per session a0daba428efc
- 10d 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 (115 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 671 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 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…