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 project-lifegit 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/project-life)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/project-life"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/project-life/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/project-life"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/project-life.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 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 12 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 12 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 114 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 166 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.00140 | $0.03067 |
| Opus 5 | $0.00070 | $0.01533 |
| Sonnet 5 | $0.00028 | $0.00613 |
| Haiku 4.5 | $0.00014 | $0.00307 |
Grade A, and why
project-life 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 9d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project life — one skill for tasks & project memory
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 create a todo or plan unless the user already asked for that in the same message.
project-life — туду, план, память. Не ран.
Цепочка
idea → todo → plan → run → merge
память: PROGRESS · LESSONS · decisions
Как открыть шпаргалку
- /lane-stack:project-life info
- каталог: /lane-stack:info
Фразы → действие
- «запиши / туду / потом / не теряй» → .agents/todos/ + INDEX
- «покажи туду» → прочитай INDEX, ответь по-русски
- «закрой / сделано / не надо» → status done/dropped
- «планируем / не запускай / обсудим» → .agents/plans/items/<slug>/, ран НЕ открывать
- «архитектор / новое приложение / сервис» → skill app-architect, artifacts/ в том же плане
- «делай / реализуй / в работу» → выход в orchestrator-lanes
- «где мы / продолж» → это resume-project, не этот скилл
План без рана
1) .agents/plans/items/<YYYY-MM-DD-slug>/ status: draft
2) Решения в PLAN.md + History. Чат не хранилище.
3) UI: в Links должен быть docs/DESIGN.md (или spawn design-lead).
4) Запрещено до «делай»: run-init, run-supervisor, Claude Plan mode, ~/.claude/plans/
Файлы
- .agents/todos/ .agents/plans/ .agents/PROGRESS.md .agents/LESSONS.md
- docs/decisions.md
- docs/plans/ = длинная стратегия, не очередь задач
На диск — English. В чат — русский. Секреты не писать.
Everything lives in files under .agents/ (project) or ~/.agents/ (global).
Durable files: English only. Chat may be Russian — answer in RU, write EN
to disk. Never put secrets in any of these files.
No orchestrator MCP. No todo_add / task CLI for ideas.
The lifecycle (one mental model)
idea ──► todo ──► plan ──► run ──► merged work
(backlog) (map) (execution) │
▼
memory: PROGRESS · LESSONS · decisions · session-log · artifacts
What ships with it
3 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.
- 9d ago First seen · 224 lines · 140 tokens per session scan A e14b08b2f397
project-life is a skill published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed today), licensed MIT. It adds 140 tokens to every session and 3,067 once invoked, about $0.0007 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.
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…
phase-wrap
Claude Code adapter for MODE: PHASE-WRAP. Delegates to the canonical opencode-swarm phase boundary protocol.