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 agentmods add agents/vkirill/claude-lane-stack/project-onboardergit clone --depth 1 https://github.com/VKirill/claude-lane-stackWhat 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 | $0.00028 | $0.01391 |
| Opus 5 | $0.00014 | $0.00696 |
| Sonnet 5 | $0.00006 | $0.00278 |
| Haiku 4.5 | $0.00003 | $0.00139 |
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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
Run
- Instructions:
~/.agents/codex/instructions/onboard.md - Schemas + checks (MUST):
~/.claude/skills/project-onboard/references/PACK-SCHEMAS.md
~/.claude/skills/project-onboard/references/VALIDATION.md
~/.claude/skills/project-onboard/references/design-md-standard.md(Google@google/design.md) - Seed + detect:
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.
- yesterday 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 (114 stars, last pushed 3d ago), licensed MIT. It adds 28 tokens to every session and 1,391 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 agents, from other repositories
rtk-testing-specialist
RTK testing expert - snapshot tests, token accuracy, cross-platform validation.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
plan-challenger
Adversarial plan review agent — read-only. Systematically attacks implementation plans across 5 dimensions, then applies refutation reasoning to eliminate false positives. Never modifies code. Use before committing to any significant implementation plan.