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 commands/sifxprime/kodelyth-ecc/onboardgit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/onboard)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/onboard"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/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.00031 | $0.00601 |
| Opus 5 | $0.00015 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/onboard — Parallel Codebase Onboarding
Three agents map your codebase simultaneously — architecture, execution paths, and documentation gaps. New to a repo? Get up to speed in 15 minutes.
What Gets Launched in Parallel
| Agent | Focus |
|---|---|
code-explorer |
Traces execution paths, maps data flow, identifies key entry points and dependencies |
architect |
Infers the architectural pattern, layers, module boundaries, and design decisions |
doc-updater |
Identifies documentation gaps, stale docs, and missing READMEs or JSDoc |
Usage
/onboard # full codebase overview
/onboard src/payments/ # focus on a specific module
/onboard --new-hire # adds kodelyth-advisor for getting-started guidance
/onboard --audit # adds code-reviewer for quality assessment
Report Format
## ONBOARDING REPORT
### Architecture (architect)
PATTERN: [MVC / hexagonal / microservices / etc.]
LAYERS: [how the code is organized]
KEY FILES: [the 5–10 files you must understand first]
DECISIONS: [notable architectural choices and why]
### Execution Paths (code-explorer)
ENTRY POINTS: [main flows — auth, data, API, jobs]
DATA FLOW: [how data moves through the system]
DEPENDENCIES: [what talks to what]
GOTCHAS: [non-obvious behaviours]
### Documentation Health (doc-updater)
MISSING: [modules with no docs]
STALE: [docs that no longer match the code]
GAPS: [API endpoints with no documentation]
---
TIME TO PRODUCTIVE: estimated X days
FIRST 3 THINGS TO READ: [ordered list]
When to Use
- First day on a new codebase
- Reviewing a large PR in an unfamiliar module
- Taking over a project from another team
- Returning to code you haven't touched in 6+ months
- Evaluating an open-source repo before adopting it
Execute Now
Invoking this command is confirmation to proceed. Execute immediately:
- Determine scope from
$ARGUMENTS. Default: entire current project. - Spawn all agents simultaneously with
run_in_background: true:code-explorer— execution path tracing and dependency mappingarchitect— architectural pattern inferencedoc-updater— documentation gap analysis
- Wait for all to complete.
- Aggregate into the Onboarding Report format above.
- End with: "Which area do you want to explore deeper first?"
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.
- 2d ago First seen · 73 lines · 31 tokens per session scan A 1542d99123ab
onboard is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 601 once invoked, about $0.0002 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-03.
Other commands, from other repositories
hatch3r-onboard
Generate a comprehensive onboarding guide for a new developer joining the project -- spawn parallel researchers to analyze codebase structure, architecture, and conventions, then produce a tailored onboarding document with setup instructions, architecture walkthrough, coding conventions, key workflows, tribal…
explain
Explain code in detail - what it does, how it works, and why.
code-tour
Generate guided codebase walkthrough with annotated reading path. Usage: /mindforge:code-tour [path] [--depth shallow|deep] [--output TOUR.md].
mindforge:edtech
Design educational technology platform. Usage: /mindforge:edtech [component] [--type lms|assessment|adaptive].
mindforge:hire
Design technical interview process. Usage: /mindforge:hire [role] [--level junior|mid|senior|staff] [--type system-design|coding|behavioral].
2Tim
Search for given words or phrases in the book of 2 Timothy in one or multiple bibles.