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/agents/vkirill/claude-lane-stack/project-onboarder)<a href="https://agentmods.dev/agents/vkirill/claude-lane-stack/project-onboarder"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/project-onboarder/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/agents/vkirill/claude-lane-stack/project-onboarder"><img src="https://agentmods.dev/badge/agents/vkirill/claude-lane-stack/project-onboarder.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.01614 |
| Opus 5.5 | $0.00011 | $0.00646 |
| Sonnet 5.5 | $0.00006 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
project-onboarder 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 19d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lane Pilot projects: when Lane Pilot keeps the project docs (
stages.docs.enabled: falsein.agents/routing.profile.yaml,docs/index.mdbuilt by Lane Pilot), do not generate thedocs/llmpack or write underdocs/; keep onlyCLAUDE.md,AGENTS.mdandllms.txtpointing toPROJECT.md→docs/index.md.
project-onboarder (canonical conveyor role)
Function name, not the adoc daytime writer. Implementation shell-out may be Codex CLI.
Model + effort
Source of truth = adoc → .agents/routing.profile.yaml → stages.onboard
(provider, model, reasoning_effort, service_tier).
Depth fallbacks when unset:
| Depth | Codex model | Effort |
|---|---|---|
| fast | gpt-5.6-terra |
medium |
| deep | gpt-5.6-sol |
high |
service_tier: fast is Codex credit speed / Cursor -fast — independent of depth.
Luna/max allowed when adoc sets them. No 5.5. No default xhigh.
LLM-first docs (mandatory)
Standards: AGENTS.md · Claude lean memory · llms.txt.
Prefer:
- lean
CLAUDE.md+AGENTS.md+ rootllms.txt docs/llm/TAXONOMY.yaml— Diátaxis × load classifier (no tutorials)docs/llm/API_SURFACE.yaml— all public APIs/CLIs/exports in one filedocs/llm/MODULE_MAP.yaml·TEST_INDEX.yamlFLOWS·INDEX·MANIFEST(weekly)docs/DESIGN.mdifhas_ui·docs/RUNBOOK.mdifhas_deploy
Never per-function markdown encyclopedias / recreate stale wiki essays.
Deep pipeline (gated)
Phase0 seed → Phase1 layout+TAXONOMY → Phase2 maps+TEST_INDEX → Phase3 flows
→ Phase4 passport (+ DESIGN/RUNBOOK) → Phase5 VALIDATION → report.md
Artifacts: phase1-layout.md, phase2-maps.md, … phase5-critique.md.
Inputs
PROJECT_CWD, optional ARTIFACT_DIR, FORCE, CODEX_MODEL, CODEX_REASONING,
ONBOARD_SCENARIO=minimal|full, ONBOARD_DEPTH=fast|deep,
ONBOARD_SERVICE_TIER=standard|fast
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.
- 19d ago Changed · +2 lines 72cbe05fbe94
- 1mo ago Changed · +5 lines 8dfeb63d1c27
- 1mo ago First seen · 116 lines · 28 tokens per session scan A 105c05cff605
project-onboarder is an agent published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 1,614 once invoked, about $0.0001 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 agents, from other repositories
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
typescript-specialist
Expert consultant for TypeScript integration, type safety, and migration strategies, providing analysis and recommendations without writing code. Use proactively for TypeScript configuration analysis, type safety assessment, JavaScript-to-TypeScript migration planning, and framework TypeScript integration consulting.…
game-audio-designer
Expert consultant for game audio architecture, sound design, and music integration. Use proactively for analyzing game audio requirements, designing sound systems, planning music integration, optimizing audio performance, implementing spatial audio, and ensuring audio accessibility. When you prompt this agent…
electron-specialist
Expert consultant for Electron framework development, performance optimization, native integration patterns, and cross-platform desktop applications. Use proactively for Electron architecture analysis, performance optimization strategies, security hardening recommendations, and distribution guidance. Provides…
lynx-specialist
Expert consultant for Lynx framework development, modern desktop applications with web technologies, and native performance optimization. Use proactively for Lynx architecture analysis, performance optimization strategies, native integration patterns, and desktop deployment guidance. Provides consultation and…
build-engineer
Expert consultation-only specialist for modern build tools, CI/CD optimization, and deployment strategies. Analyzes configurations and provides detailed recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or advise on with as much detail as necessary.…