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.
git clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/nolabs-ai/claude-extensions/onboarding)<a href="https://agentmods.dev/commands/nolabs-ai/claude-extensions/onboarding"><img src="https://agentmods.dev/badge/commands/nolabs-ai/claude-extensions/onboarding.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.00009 | $0.00730 |
| Opus 5 | $0.00005 | $0.00365 |
| Sonnet 5 | $0.00002 | $0.00146 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
onboarding 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 7d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Onboarding Guide
Generate a comprehensive onboarding document for new developers joining the project.
Process
-
Analyze Project
- Read README.md and existing documentation
- Examine package.json/requirements.txt for dependencies
- Identify key configuration files
-
Document Setup
- Prerequisites
- Installation steps
- Environment configuration
- Running locally
-
Explain Architecture
- Project structure
- Key components
- Data flow
- Important patterns
-
Identify Key Areas
- Critical code paths
- Common development tasks
- Testing approach
- Deployment process
Output Format
Onboarding Guide: [Project Name]
Prerequisites
Before you begin, ensure you have:
- [Runtime] version X.X or higher
- [Database] running locally or access to dev instance
- [Other tools]
Getting Started
1. Clone the Repository
git clone [repo-url]
cd [project-name]
2. Install Dependencies
npm install
# or
pip install -r requirements.txt
3. Configure Environment
cp .env.example .env
# Edit .env with your settings
Required environment variables:
DATABASE_URL- Connection string for databaseAPI_KEY- API key for [service]
4. Run the Application
npm run dev
# or
python manage.py runserver
The app will be available at http://localhost:3000
Project Structure
[project-name]/
├── src/
│ ├── components/ # UI components
│ ├── services/ # Business logic
│ ├── utils/ # Helper functions
│ └── index.js # Entry point
├── tests/ # Test files
└── docs/ # Documentation
Key Concepts
[Concept 1]
[Explanation of important concept]
[Concept 2]
[Explanation of important concept]
Development Workflow
Running Tests
npm test
Code Style
We use [ESLint/Prettier/Black] for code formatting.
npm run lint
Creating a Branch
git checkout -b feature/your-feature
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.
- 7d ago First seen · 155 lines · 9 tokens per session scan A 8f5ba5f1dfa1
onboarding is a command published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 9 tokens to every session and 730 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.