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/oxygen-fragment/claude-modular/setup-environmentgit clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/oxygen-fragment/claude-modular/setup-environment)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/setup-environment"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/setup-environment.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.00000 | $0.00598 |
| Opus 5 | $0.00000 | $0.00299 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
setup-environment 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.
What it actually says
Setup Environment Command
2. **Dependency Installation**
- Install runtime dependencies
- Set up development dependencies
- Configure package managers
- Install global tools and utilities
3. **Configuration Setup**
- Generate environment configuration files
- Set up IDE/editor configurations
- Configure linting and formatting tools
- Initialize pre-commit hooks
4. **Database and Services**
- Set up local database instances
- Configure external service connections
- Initialize data seeding
- Set up monitoring and logging
5. **Tool Configuration**
- Configure test runners
- Set up build tools and bundlers
- Initialize documentation tools
- Configure deployment tools
6. **Verification**
- Run health checks
- Execute test suite
- Verify build process
- Check service connectivity
# Actions performed:
# - npm install / yarn install
# - Configure .env files
# - Set up pre-commit hooks
# - Initialize database
# - Run initial tests
```
```bash
# Setup with specific database
/project:setup-environment --database=postgresql
# Additional actions:
# - Install PostgreSQL client
# - Create development database
# - Run migrations
# - Seed initial data
```
```bash
# Team setup with shared configuration
/project:setup-environment --team-config
# Includes:
# - Shared IDE settings
# - Team-wide linting rules
# - Consistent formatting
# - Shared Git hooks
```
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 · 99 lines · 0 tokens per session scan A 16c0c7d9746f
setup-environment is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 598 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
paul:help
Show available PAUL commands and usage guide.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
test
Smart test runner with filtering, coverage, and health monitoring.
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.