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.
git clone --depth 1 https://github.com/AGoldian/claudenvWrote 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/agoldian/claudenv/init-docs)<a href="https://agentmods.dev/commands/agoldian/claudenv/init-docs"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/init-docs/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/agoldian/claudenv/init-docs"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/init-docs.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.00009 | $0.01066 |
| Opus 5.5 | $0.00004 | $0.00426 |
| Sonnet 5.5 | $0.00002 | $0.00213 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
init-docs 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Documentation Generator
You are generating Claude Code documentation for this project. Follow the phases below carefully.
Phase 1: Project Analysis
Scan the project to detect the tech stack. Read the following detected files:
Package managers and manifests:
!find . -maxdepth 3 \( -name "package.json" -o -name "pyproject.toml" -o -name "go.mod" -o -name "Cargo.toml" -o -name "Gemfile" -o -name "composer.json" -o -name "pom.xml" -o -name "build.gradle*" -o -name "*.csproj" \) -not -path "*/node_modules/*" 2>/dev/null | head -20
Framework configs:
!find . -maxdepth 2 \( -name "tsconfig.json" -o -name "next.config.*" -o -name "vite.config.*" -o -name "nuxt.config.*" -o -name "svelte.config.*" -o -name "astro.config.*" -o -name "angular.json" -o -name "manage.py" -o -name "docker-compose.*" \) -not -path "*/node_modules/*" 2>/dev/null | head -20
CI/CD:
!find . -maxdepth 3 \( -path "*/.github/workflows/*" -o -name ".gitlab-ci.yml" -o -name "Jenkinsfile" -o -name ".circleci/config.yml" \) 2>/dev/null | head -10
Existing documentation:
!find . -maxdepth 2 \( -name "README.md" -o -name "CLAUDE.md" -o -name "CONTRIBUTING.md" \) -not -path "*/node_modules/*" 2>/dev/null | head -10
Read the manifest files you found above to understand dependencies, scripts, and project structure.
Phase 2: Clarifying Questions
Based on your analysis, ask the user these questions ONE AT A TIME, waiting for each answer before proceeding to the next:
- Project description: "What is the primary purpose of this project?" (e.g., SaaS web app, REST API, CLI tool, shared library)
- Deployment: "What deployment target does this project use?" (e.g., Vercel, AWS, Docker, bare metal, not yet decided)
- Conventions: "Are there any team conventions not captured in config files?" (naming patterns, branching strategy, PR process, coding standards)
- Focus areas: "What areas of the codebase should Claude pay special attention to?" (critical business logic, complex algorithms, areas prone to bugs)
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 · 70 lines · 9 tokens per session scan A 471edf71e628
init-docs is a command published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,066 once invoked, about $0.0000 per session on Opus 5.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
doctor
Use when the user invokes /goal-flight doctor to check Goal Flight host and project readiness.
interactive-dev
Start a persistent interactive development session with natural language browser control, auto-error monitoring, and full dev tool access.
graduate
Graduate a Lovable / Bolt / v0 export to GitHub Actions + a non-platform deploy target via the Starter Series 5-step path. Orchestrates the three audit MCP tools and surfaces lift-in steps for the matching starter.
figma-design-to-code
Implement a Figma frame, file, or selection as production code with pixel-exact fidelity.
sugar-review
Review and manage pending Sugar tasks interactively.
sugar-task
Create a comprehensive Sugar task with rich context and metadata.