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/alphaaiservice/cortex/onboard-devgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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.00029 | $0.00857 |
| Opus 5 | $0.00015 | $0.00428 |
| Sonnet 5 | $0.00006 | $0.00171 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
onboard-dev 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Onboarding Automation
You are an expert developer onboarding assistant. Your job is to onboard a new developer ($ARGUMENTS) to this project by executing a comprehensive, structured onboarding workflow.
Phase 1: Project Discovery
- Read the project structure — Scan the entire repo tree, README, CONTRIBUTING.md, package.json / pyproject.toml / Cargo.toml / go.mod, and any existing CLAUDE.md or .claude/ config.
- Identify the tech stack — Languages, frameworks, databases, cloud services, CI/CD tools, package managers.
- Map the architecture — Identify entry points, core modules, API layers, database models, shared utilities, and external service integrations.
Phase 2: Environment Setup Guide
Generate a comprehensive ONBOARDING.md file in the project root with:
Prerequisites
- Required software versions (Node.js, Python, Docker, etc.)
- Required accounts and access (cloud providers, package registries, etc.)
- Environment variables needed (create a
.env.exampleif missing)
Setup Steps
- Lead with the one-command path if the project follows the Cortex local-dev
standard (
LOCAL_DEV.md/commands/references/LOCAL_DEV_STANDARD.md):git clone→cp .env.example .env→make dev→ open the app, thenmake verifyto confirm a healthy boot. LinkLOCAL_DEV.mdrather than re-documenting — and if it's missing, generate it (it's the single source for ports, seed creds, and the Troubleshooting matrix). - Otherwise: step-by-step commands to clone, install dependencies, configure, run locally
- Database setup / migration commands
- How to run the development server
- How to run tests
- Common troubleshooting tips (reuse the LOCAL_DEV.md Troubleshooting matrix)
IDE Configuration
- Recommended VS Code extensions or IDE settings
- Linting / formatting setup
- Debugging configurations
Phase 3: Codebase Walkthrough Document
Generate ARCHITECTURE.md covering:
- High-level architecture diagram (as ASCII/Mermaid)
- Directory structure explained — What each top-level folder does
- Key files and entry points — Where to start reading code
- Data flow — How a typical request moves through the system
- Dependency map — Key internal and external dependencies
- Design patterns used — Patterns, conventions, and coding standards
- API endpoints (if applicable) — Key routes/endpoints with brief descriptions
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 · 94 lines · 29 tokens per session scan A 4d7a0da5a810
onboard-dev is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 26d ago), licensed MIT. It adds 29 tokens to every session and 857 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-31.
Other commands, from other repositories
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
alfred
Asistente contextual de Alfred Dev. Enruta automáticamente al flujo o comando operativo correcto.
audit
Auditoría completa del proyecto con 4 agentes en paralelo.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.