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 skills add panbanda/omen --skill onboard-codebasegit clone --depth 1 https://github.com/panbanda/omenWrote 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/skills/panbanda/omen/onboard-codebase)<a href="https://agentmods.dev/skills/panbanda/omen/onboard-codebase"><img src="https://agentmods.dev/badge/skills/panbanda/omen/onboard-codebase/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/skills/panbanda/omen/onboard-codebase"><img src="https://agentmods.dev/badge/skills/panbanda/omen/onboard-codebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00813 |
| Opus 5.5 | $0.00014 | $0.00325 |
| Sonnet 5.5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
onboard-codebase 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 1mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Onboard Codebase
Generate a comprehensive onboarding guide for a new developer joining the project, identifying key code, architecture, and people to talk to.
Prerequisites
Omen CLI must be installed and available in PATH.
Workflow
Step 1: Get a Quick Code Map
Run the outline command for a token-cheap overview of every file's structure:
omen -f json outline --compact --top 50
This returns imports, classes with methods, and top-level functions — much cheaper than reading full source files.
Step 2: Identify Key Symbols
Run the repomap analysis to find the most important code:
omen -f json repomap --compact --top 25
PageRank-ranked symbols show what's central to the codebase.
Step 3: Map the Architecture
Run the dependency graph analysis to understand structure:
omen -f json graph
This reveals how the codebase is organized and how modules relate.
Step 4: Identify Subject Matter Experts
Run the ownership analysis to find who knows what:
omen -f json ownership
This shows who has expertise in each area of the code.
Step 5: Find Complexity Hotspots
Run the complexity analysis to identify tricky areas:
omen -f json complexity
New developers should be warned about complex areas.
Output Format
Generate an onboarding guide:
# Onboarding Guide: <Project Name>
## Quick Start
1. Clone the repo: `git clone ...`
2. Install dependencies: `...`
3. Run tests: `...`
4. Start dev server: `...`
## Architecture Overview
### Module Structure
src/ ├── core/ # Core business logic ├── api/ # HTTP handlers ├── storage/ # Database layer └── utils/ # Shared utilities
### Key Dependencies
- `core/` depends on `storage/`
- `api/` depends on `core/`
- `utils/` is shared by all
## Important Code to Understand
### Core Symbols (by importance)
1. `core.Engine` - Main processing engine, heart of the system
2. `api.Router` - HTTP routing and middleware
3. `storage.Repository` - Database abstraction
4. ...
### Entry Points
- `cmd/server/main.go` - Main server entry point
- `cmd/worker/main.go` - Background job processor
## Subject Matter Experts
| Area | Expert | Notes |
|------|--------|-------|
| Core engine | [email protected] | Original author |
| API layer | [email protected] | Recent maintainer |
| Storage | [email protected] | Database specialist |
## Areas to Be Careful With
### High Complexity
- `core/processor.go` - Cognitive complexity: 45
- Talk to alice before modifying
- Has many edge cases
- `api/middleware.go` - Cyclomatic complexity: 28
- Authentication logic is tricky
- Well-tested but fragile
### Knowledge Silos
- `legacy/importer.go` - Only one contributor
- Documentation is sparse
- Ask alice for context
## First Tasks Suggestions
Good starter tasks to learn the codebase:
1. Add a new API endpoint (learn api/ patterns)
2. Write tests for an untested function (learn testing patterns)
3. Fix a documentation issue (explore while reading)
4. Address a simple TODO/FIXME (learn code style)
## Resources
- Design docs: `docs/design/`
- API docs: `docs/api/`
- Team wiki: <link>
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.
- 1mo ago First seen · 145 lines · 35 tokens per session scan A eb310555e721
onboard-codebase is a skill published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 813 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 skills, from other repositories
find-docs
Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training…
context7-cli
Use the ctx7 CLI to fetch library documentation and configure Context7 MCP. Activate when the user mentions "ctx7" or "context7", needs current docs for any library, or needs to set up Context7 for their AI coding agent.
context7-mcp
This skill should be used when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks like React, Vue, Next.js, Prisma, Supabase, etc.
context7-docs
Fetch up-to-date documentation and code examples for any library, framework, SDK, CLI tool, or cloud service. Use whenever the user asks about a specific library — even well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot — because training data may not reflect recent API changes or…
image-to-3d
Turn a generated or photographed image of a single object into a 3D mesh with the Tripo API, and download the GLB. Use when the request involves image-to-3D, photogrammetry-style reconstruction, turning a product shot or an isolated garment, prop or piece of hardware into a model for Blender, Unity or Unreal, or when…
character-reference-sheets
Dress 3D character base renders with AI-generated clothing while preserving the body, pose and framing, so each garment can be cut out and sent to image-to-3D generators. Use when the request involves a Blender base render in A-pose or T-pose, a character visual sheet, a turnaround, generating clothing over a nude…