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.
git 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/commands/vkirill/claude-lane-stack/project-onboard)<a href="https://agentmods.dev/commands/vkirill/claude-lane-stack/project-onboard"><img src="https://agentmods.dev/badge/commands/vkirill/claude-lane-stack/project-onboard.svg" alt="Measured on agentmods" 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.00018 | $0.00431 |
| Opus 5 | $0.00009 | $0.00216 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
project-onboard 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 7d 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.
What it actually says
Онбординг репозитория делает project-onboarder (не Grok). Fable не пишет CLAUDE.md руками.
Args
$ARGUMENTS may include path and flags:
- path to repo (default: cwd)
deep/fast— depth overridefull/minimal— scenario override
Examples: /project-onboard · /project-onboard deep · /project-onboard /path/to/repo fast
Steps
PROJECT_CWD= path from args or cwd (absolute).- Parse depth/scenario from
$ARGUMENTS→ONBOARD_DEPTH,ONBOARD_SCENARIOif present. - Spawn Agent → project-onboarder:
PROJECT_CWD: <abs>
ARTIFACT_DIR: <abs>/.agents/runs/_onboard/artifacts/001
FORCE: 0
ONBOARD_DEPTH: deep|fast # if user asked; else omit (auto: full→deep, minimal→fast)
ONBOARD_SCENARIO: full|minimal # only if user asked
-
Wait for finish. Read:
.agents/onboard.scenario.yamlARTIFACT_DIR/report.md- skim
CLAUDE.md(must not be “Edit me”)
-
Reply in Russian:
- scenario + depth + score
- files created/updated
- verify result (if deep)
- wiki mismatches
- gaps / next step
-
If depth was deep but report is thin (no MODULES_READ / still stub CLAUDE) → say partial and offer re-run
--deep.
Do not implement product features in this command.
If codex CLI missing: run project-onboard shell seed only, warn that deep fill needs Codex/agent write path.
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.
- 7d ago First seen · 48 lines · 18 tokens per session scan A a155ec9c5e4f
project-onboard is a command published in the GitHub repository VKirill/claude-lane-stack (115 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 431 once invoked, about $0.0001 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 commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
init-docs
Fetch official Anthropic Claude Code docs and store as local baseline snapshot.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
minar-referencias
Buscar repos open-source relevantes como referencia antes de implementar.