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/validate-docs)<a href="https://agentmods.dev/commands/agoldian/claudenv/validate-docs"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/validate-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/validate-docs"><img src="https://agentmods.dev/badge/commands/agoldian/claudenv/validate-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.00007 | $0.00305 |
| Opus 5.5 | $0.00003 | $0.00122 |
| Sonnet 5.5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
validate-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.
What it actually says
Validate Project Documentation
Run validation checks on the project's Claude Code documentation.
Step 1: Run Bash Validation
Execute the validation script:
!bash .claude/skills/doc-generator/scripts/validate.sh 2>&1 || true
Step 2: Deep Validation
Perform additional checks that require reading file contents:
-
Read CLAUDE.md and verify:
- All
@importreferences resolve to existing files - Commands in the ## Commands section match actual scripts in package.json / pyproject.toml / Makefile
- Directories in ## Architecture section actually exist
- All
-
Read .claude/rules/*.md files and verify:
- YAML frontmatter
pathsglobs match files that exist in the project - Referenced tools (linters, formatters, test frameworks) are actually installed
- YAML frontmatter
-
Read .claude/settings.json and verify:
- Valid JSON structure
- Referenced hook scripts exist at the specified paths
Step 3: Report
Present a clear summary:
- List all errors (things that must be fixed)
- List all warnings (things that should be reviewed)
- Provide a pass/fail verdict
If there are errors, suggest specific fixes for each one.
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 · 41 lines · 7 tokens per session scan A ce6014f790ef
validate-docs is a command published in the GitHub repository AGoldian/claudenv (10 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 305 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.