Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/cassler/awesome-claude-code-setupnpx agentmods add commands/cassler/awesome-claude-code-setup/post-init-onboardingWrote 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/cassler/awesome-claude-code-setup/post-init-onboarding)<a href="https://agentmods.dev/commands/cassler/awesome-claude-code-setup/post-init-onboarding"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/post-init-onboarding/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/commands/cassler/awesome-claude-code-setup/post-init-onboarding"><img src="https://agentmods.dev/badge/commands/cassler/awesome-claude-code-setup/post-init-onboarding.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00446 |
| Opus 5.5 | $0.00000 | $0.00178 |
| Sonnet 5.5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
post-init-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 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.
What it actually says
Post-Init Onboarding & Setup
Complete the onboarding process for this codebase:
1. Environment Setup
-
Verify .env configuration
- Check all required API keys are present
- Validate environment-specific settings
- Ensure secrets are properly protected
-
Test service connectivity
make dev # Start all services make test # Run health checks
2. Run Setup Scripts
-
Database initialization
- Check if schemas are properly applied
- Verify initial data is loaded
- Test database connections
-
Import initial data
# Run any data import or setup scripts found in the project # Examples: ./scripts/setup.sh, npm run setup, make init
3. Verify Core Functionality
-
Access all services
- Check README or documentation for service URLs
- Verify each service is accessible
- Test authentication if required
-
Test key workflows
- Execute main functionality
- Verify data flows correctly
- Check monitoring/logging systems
4. Q&A Session
Answer these questions to ensure understanding:
-
Architecture Questions
- How do services communicate?
- What's the main data flow through the system?
- Where are key resources stored and managed?
-
Development Questions
- What's the typical development workflow?
- How do you extend core functionality?
- Where do you add new API endpoints or features?
-
Deployment Questions
- How does CI/CD work?
- What's different in production config?
- How are secrets managed?
5. Quick Wins
Identify and implement 2-3 quick improvements:
- Fix any setup issues discovered
- Add missing documentation
- Improve developer experience
- Clean up any warnings or errors
6. Create Personal Notes
Document:
- Your development environment setup
- Any gotchas or workarounds needed
- Useful commands or shortcuts discovered
- Questions for the team
This onboarding ensures you're fully set up and understand the codebase before diving into feature work!
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 · 78 lines · 0 tokens per session scan A 9e68680ad98b
post-init-onboarding is a command published in the GitHub repository cassler/awesome-claude-code-setup (268 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 446 tokens. 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 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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.