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/agoldian/claudenv/whygit clone --depth 1 https://github.com/AGoldian/claudenvWhat 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.00025 | $0.00299 |
| Opus 5 | $0.00013 | $0.00150 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
why 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 2d 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
/why — Краткое объяснение
Объяснить $ARGUMENTS в контексте текущей задачи. Не вызывает vibe-decisions, не пишет в ~/.claudenv/memories/decisions/.
Step 1 — Check canon first
Run claudenv canon search "$ARGUMENTS" (Bash). If matches found — упомяни их как primary references.
Step 2 — Brief explanation (3-5 lines)
Структура:
- Что это: 1 строка
- Когда используется: 1-2 строки
- Когда не подходит: 1 строка
- Ссылки (опционально): канон или WebSearch если канон пуст
Не делать
- Не выводи vibe-decisions overview format (это explainer, не decision)
- Не пиши файл в decisions/
- Если пользователь после
/whyначинает реальный выбор технологии — тогда уже триггерится vibe-decisions skill
Style
- User's language
- Краткость > полнота. Для полноты есть
/deeperпосле реального decision.
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.
- 2d ago First seen · 34 lines · 25 tokens per session scan A f2fae0e91441
why is a command published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 299 once invoked, about $0.0001 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
test-e2e
Write end-to-end tests for critical user journeys.
test-integration
Write integration tests for component boundaries.
export
Design public API exports.
newpkg
Generate new package with Nx.
init
Initialize goal-flight state for a project.
index
Command "index" from cesarandreslopez/tauri-agent-tools, covering command reference, command summary, categories, visual capture and dom inspection.