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 skills/huzaifa525/claude-code-optimizer/onboardnpx skills add huzaifa525/claude-code-optimizer --skill onboardgit clone --depth 1 https://github.com/huzaifa525/claude-code-optimizerWrote 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/huzaifa525/claude-code-optimizer/onboard)<a href="https://agentmods.dev/skills/huzaifa525/claude-code-optimizer/onboard"><img src="https://agentmods.dev/badge/skills/huzaifa525/claude-code-optimizer/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 | $0.00025 | $0.00586 |
| Opus 5 | $0.00013 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
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 5d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate a complete onboarding guide for this project.
Analyze
-
Project basics
- Read package.json / pyproject.toml / Cargo.toml / go.mod
- Identify language, framework, database, key dependencies
- Read README if it exists
-
Project structure
- Scan top-level directories
- Identify source, test, config, build, and doc directories
- Map the architecture
-
Entry points
- Find main/index files
- Find route definitions
- Find configuration files
-
Development workflow
- Read scripts in package.json
- Check for Makefile, docker-compose, CI config
- Identify how to run, test, build, deploy
-
Code conventions
- Read linter configs (.eslintrc, .prettierrc, ruff.toml, etc.)
- Check existing CLAUDE.md or .editorconfig
- Sample 3-4 files to identify patterns
-
Git workflow
- Check branch naming from recent branches
- Read git log for commit message style
- Check for PR templates (.github/pull_request_template.md)
Output
# Onboarding Guide: [Project Name]
## Quick Start
1. Clone: `git clone [url]`
2. Install: `[install command]`
3. Setup: `[env setup, db setup]`
4. Run: `[dev command]`
5. Test: `[test command]`
## Architecture
[High-level architecture diagram/description]
## Project Structure
[Directory map with purpose of each]
## Key Files
[Entry points and important files]
## Tech Stack
| Category | Technology |
|----------|-----------|
| Language | [X] |
| Framework | [X] |
| Database | [X] |
| Testing | [X] |
## Development Workflow
[How to create branches, commit, PR]
## Code Conventions
[Naming, structure, patterns used]
## Common Tasks
- Add a new API endpoint: [steps]
- Add a new component: [steps]
- Add a new test: [steps]
- Run specific tests: [command]
## Environment Variables
[Required env vars and what they do]
## Useful Commands
| Command | What It Does |
|---------|-------------|
| [cmd] | [description] |
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.
- 5d ago First seen · 95 lines · 25 tokens per session scan A 38ff89a2e843
onboard is a skill published in the GitHub repository huzaifa525/claude-code-optimizer (9 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 586 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 skills, from other repositories
agent-newbie-guide
Skill "agent-newbie-guide" from hashgraph-online/awesome-codex-plugins, covering codex 新手引导, 🚫 新手术语过滤（绝对禁止）, 统一行为规范（内嵌）, 📍 阶段位置 and 启动自检.
memstack-marketing-webinar-script
Use this skill when the user says 'webinar script', 'webinar', 'live presentation', 'teach-to-sell', or needs a timestamped presentation script with slide notes, presenter cues, and replay email sequence. Do NOT use for launch plans or static sales page copy.
moai-workflow-jit-docs
Enhanced Just-In-Time document loading system that discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation on demand.
memstack-development-mentor
Use when the user says 'teach me', 'explain as you go', 'mentor mode', 'walk me through', 'help me learn', 'explain why', 'learning mode', or wants real-time plain language narration of decisions and tradeoffs while building. Do NOT use for code review or debugging.
map-learn
Capture reusable lessons after a completed MAP workflow. Use when a MAP run has finished and you want rules written to .claude/rules/learned/ from a workflow summary or handoff. Do NOT use during active implementation.
map-understand
Interactive deep-understanding and quiz mode for MAP sessions. Use when the user wants to understand code, a diff, workflow result, debugging cause, or architecture and be checked with restatements or quizzes.