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 project-initgit 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/project-init)<a href="https://agentmods.dev/skills/claude-world/director-mode-lite/project-init"><img src="https://agentmods.dev/badge/skills/claude-world/director-mode-lite/project-init.svg" alt="Measured on agentmods" 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.00039 | $0.00553 |
| Opus 5 | $0.00019 | $0.00277 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
project-init 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 8d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project initialization
Create the smallest useful project context without adding permission gates, blocking hooks, or mandatory process rules.
1. Inspect before writing
- Read existing
CLAUDE.md,AGENTS.md, README, manifests, scripts, and CI. - Detect the language, framework, build, test, lint, and development commands from repository evidence.
- Preserve existing user guidance and unrelated configuration.
- If the stack or desired workflow cannot be inferred safely, ask one focused question instead of inventing it.
2. Add concise shared context
Keep permanent guidance focused on facts useful in most sessions:
# Project name
## Purpose
[What this repository delivers]
## Stack and structure
- [Language/framework]
- [Important entry points]
## Commands
- dev: [verified command]
- test: [verified command]
- build: [verified command]
- lint: [verified command]
## Local conventions
- [Only repository-specific conventions supported by evidence]
Use the Director managed block in both CLAUDE.md and AGENTS.md so all three
CLIs can find .director-mode/GUIDANCE.md. Put detailed, conditional procedures
in skills rather than expanding the permanent files.
3. Verify native assets
Check the selected CLI surfaces:
Claude: .claude/skills/ and .claude/agents/
Codex: .agents/skills/ and .codex/agents/
Grok: shared Claude-compatible skills and .grok/agents/
Relay: .director-mode/bin/director-relay
Run scripts/verify-install.sh when available. Do not require every optional
tool merely to declare setup complete.
4. Optional integrations
MCP servers, hooks, TDD, autonomous loops, and extra agents are choices, not defaults. Suggest one only when it materially helps the current repository and explain its effect. Install or register it only after the user requests it.
In particular, never register a Stop hook, deny rule, validator, security guard, or background tracker as part of ordinary project initialization.
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.
- 8d ago First seen · 77 lines · 39 tokens per session scan A 9d8627aaef12
project-init is a skill published in the GitHub repository claude-world/director-mode-lite (81 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 553 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.