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 claude-world/director-mode-lite --skill check-environmentgit clone --depth 1 https://github.com/claude-world/director-mode-liteWrote 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/claude-world/director-mode-lite/check-environment)<a href="https://agentmods.dev/skills/claude-world/director-mode-lite/check-environment"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/check-environment/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/claude-world/director-mode-lite/check-environment"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/check-environment.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.00044 | $0.00918 |
| Opus 5 | $0.00022 | $0.00459 |
| Sonnet 5 | $0.00009 | $0.00184 |
| Haiku 4.5 | $0.00004 | $0.00092 |
Grade A, and why
check-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 9d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Check
Verify your development environment is ready for Director Mode.
Checks Performed
1. Director Mode Dependencies
| Tool | Purpose | Check | Required |
|---|---|---|---|
| git | Version control | git --version |
Yes |
| python3 | Installer, adapters, and relay | python3 --version |
Yes |
| jq | Legacy automation hooks only | jq --version |
No |
2. CLI versions
claude --version
codex --version
grok --version
Minimum: 2.0.0+
3. Project-Specific Tools
Auto-detect project type and check relevant tools:
| Project Type | Detected By | Tools to Check |
|---|---|---|
| Node.js | package.json |
node --version, npm --version or pnpm --version |
| Python | requirements.txt, pyproject.toml |
python3 --version, pip --version |
| Rust | Cargo.toml |
rustc --version, cargo --version |
| Go | go.mod |
go version |
| Java | pom.xml, build.gradle |
java --version, mvn --version or gradle --version |
4. Director Mode Installation
-
.claude/directory exists -
.claude/skills/populated (35 skills expected) -
.agents/skills/populated when the Codex adapter is selected -
.director-mode/bin/director-relayis executable -
.director-mode/bin/director-openis executable -
.claude/agents/populated (14 agents expected) -
.codex/agents/and.grok/agents/populated for selected adapters - no active hooks for the default install
- optional hooks match the explicitly selected mode and contain no surprise deny/block response
-
CLAUDE.mdexists
5. Git Status
- Inside git repository
- Clean working tree (or note uncommitted changes)
Output Format
## Environment Check Results
### Director Mode Dependencies
- [x] git: 2.39.0
- [x] python3: 3.11.0
- [x] jq: 1.7
### Claude Code
- [x] Version: 2.1.201
### Project Tools (Node.js detected)
- [x] node: 20.10.0
- [x] pnpm: 8.12.0
### Director Mode Installation
- [x] .claude/ directory exists
- [x] 35 skills installed
- [x] Cross-CLI guidance and relay installed
- [x] 14 agents installed
- [x] default hook mode: none
- [x] native open launcher installed
- [x] CLAUDE.md exists
### Git Status
- [x] Git repository initialized
- [ ] Warning: 3 uncommitted changes
### Summary
**Status**: Ready
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.
- 9d ago First seen · 112 lines · 44 tokens per session scan A 5129994acd01
check-environment is a skill published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 9d ago), licensed MIT. It adds 44 tokens to every session and 918 once invoked, about $0.0002 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-30.
Other skills, from other repositories
concise
Concise communication mode. Cuts 60-70% of output tokens while keeping natural, readable English. Drops filler, hedging, and pleasantries but maintains grammar and sentence flow. Elaborate on request -- ask for detail and get it, then auto-return to concise. Use when user says "concise mode", "be concise", "less…
peekaboo
Provides runtime observation and interaction for native macOS interfaces through accessibility state and screenshots. Use when the task depends on visible or interactive state in a running SwiftUI/AppKit app: what is rendered, focused, selected, enabled, reachable through menus/windows/dialogs, or experienced across a…
mobile-flows-maestro
This skill should be used when Maestro is explicitly requested or already present and the task is to author, run, or debug iOS/Android Maestro flows; use Maestro MCP; or handle Maestro selectors, system UI, permissions, Keychain, JavaScript, waits, device state, flakiness, or CI. Evidence includes a .maestro directory…
validate-mobile
Run a Maestro flow on an explicitly selected iOS or Android device and report behavioral evidence.
validate-api
Run the project's Hurl scenarios with an OIDC access token passed as a secret variable.
kanso-audit
Use when the user asks for a code review, audit, pre-PR check, quality sweep, or pattern analysis of a diff, branch, module, or codebase. Also use when the user asks to "check" or "look over" their code for issues.