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 seo-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/seo-project-life)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/seo-project-life"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/seo-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/seo-project-life"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/seo-project-life.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 analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00110 | $0.01310 |
| Opus 5 | $0.00055 | $0.00655 |
| Sonnet 5 | $0.00022 | $0.00262 |
| Haiku 4.5 | $0.00011 | $0.00131 |
Grade A, and why
seo-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 5d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO project life — where things live
Info (print and stop)
If $ARGUMENTS is info, or the user says info / справка / где seo this skill:
print the block below verbatim (Russian), then stop.
seo-project-life — карта SEO-проекта. Не код.
Два слоя (не путать)
1) Жизнь проекта → <repo>/.agents/seo/<slug>/
2) Каталог умений → ~/.agents/seo-system/modules/ (CLI: seo-module)
Цепочка
passport → discovery → strategy → technical → content → offpage → measure
Как открыть
- /lane-stack:seo-project-life info
- агент: cc s / claude --agent seo-specialist
- настройки API/моделей: seodoc
Фразы → действие
- «где мы / продолж» → seo-resume .
- «пустой harness» → seo-init <slug> --domain …
- «живой сайт с нуля» → seo-module playbook live-site-start
- «сайта ещё нет» → seo-module playbook greenfield-start
- «одна статья» → seo-module playbook one-article
- «какой модуль» → seo-module list затем seo-module scenario <mod> <scen>
- «после работы» → seo-board . && seo-handoff-write .
Куда писать
- факты проекта STATUS.md / ANAMNESIS.md / passport/
- исследование discovery/
- стратегия/кокон strategy/
- техника technical/ (код сайта → .agents/runs/ + dev-orchestrator)
- черновики/GIST content/
- ссылки/бренд offpage/
- цифры/SERP measurement/ evidence/serp/
- прогон промпта prompts-used/log.tsv
На диск — English keys. В чат — русский. Секреты не писать.
Two layers
| Layer | Path | What it is |
|---|---|---|
| Project life | <repo>/.agents/seo/<slug>/ |
This client's state. Disk is SoT. |
| Capability catalog | ~/.agents/seo-system/ |
18 modules + playbooks. Not per-project. |
| CLI | ~/.agents/bin/seo-* |
seo-resume, seo-module, seo-dispatch, … |
| Settings | seodoc |
Providers, OpenRouter models, stage agents |
| Originals | skill seo-prompt-engineering-2026 |
Open 1:1, never rewrite |
If ~/.agents/seo-system/modules is missing: the catalog is not installed.
Do not invent playbooks. Tell the human to rerun lane-stack ./install.sh
(or seo-orchestration ./install.sh). Then seo-module list.
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.
- 5d ago First seen · 130 lines · 110 tokens per session scan A cacc14f84b71
seo-project-life is a skill published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,310 once invoked, about $0.0006 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-09-05.
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…