Borrowing it
Nothing to install: this file belongs to glassBead-tc/widescreen-research. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/glassBead-tc/widescreen-research/main/.claude/commands/games/docs-improvement-game.mdgit clone --depth 1 https://github.com/glassBead-tc/widescreen-researchWrote 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/glassbead-tc/widescreen-research/docs-improvement-game)<a href="https://agentmods.dev/commands/glassbead-tc/widescreen-research/docs-improvement-game"><img src="https://agentmods.dev/badge/commands/glassbead-tc/widescreen-research/docs-improvement-game/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/glassbead-tc/widescreen-research/docs-improvement-game"><img src="https://agentmods.dev/badge/commands/glassbead-tc/widescreen-research/docs-improvement-game.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.00000 | $0.07162 |
| Opus 5 | $0.00000 | $0.03581 |
| Sonnet 5 | $0.00000 | $0.01432 |
| Haiku 4.5 | $0.00000 | $0.00716 |
Grade C, and why
docs-improvement-game scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .docs-game/ How it starts
The opening of the file, as written. The whole thing — 807 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Improvement Game
Game-theoretic documentation workflow that systematically discovers API gaps, prevents perfectionism spirals, and ships production-ready documentation using parallel execution and validation gates.
Command Structure
/docs-improvement-game [DOCS] [CODEBASE] [SPECS] [--SCOPE=<scope>] [--BUDGET=<hours>] [--STRATEGY=<strategy>] [--PARALLEL=<count>]
Parameter Definitions
DOCS: Location of the documentation database to be updatedCODEBASE: Location of the codebase DOCS is aboutSPECS: Markdown file, or collection of markdown files, expressing the desired end state of the full intended workflow.TOPIC(optional): Specific API/topic to document (auto-discovered if not provided)SCOPE: Analysis scope (sdk, cli, docs, all) - default: allBUDGET: Time budget in hours (default: 4)STRATEGY: Implementation approach (sequential, parallel, hybrid) - default: hybridPARALLEL: Number of parallel worktrees for implementation (default: 3)
Game Variables
DOCS: $ARGUMENTS CODEBASE: $ARGUMENTS SPECS: $ARGUMENTS TOPIC: $ARGUMENTS SCOPE: $ARGUMENTS BUDGET: $ARGUMENTS STRATEGY: $ARGUMENTS PARALLEL: $ARGUMENTS
Phase 1: Discovery & Gap Analysis (Time-boxed: 40% of budget)
Objective: Find the highest-value documentation gaps
# Initialize game state
echo "🎮 Starting Docs Improvement Game"
echo "⏰ Budget: $BUDGET hours"
echo "🎯 Scope: $SCOPE"
mkdir -p .docs-game/{state,analysis,candidates}
cat > .docs-game/state.json << 'EOF'
{
"phase": "discovery",
"budget_remaining": $BUDGET,
"commitment_level": 0,
"spiral_detections": [],
"candidates": [],
"active_implementations": [],
"players": {
"perfectionist": { "satisfaction": 0.0, "weight": 0.7 },
"shipper": { "urgency": 0.3, "weight": 0.9 },
"user_advocate": { "value_focus": 0.8, "weight": 1.0 },
"maintainer": { "sustainability": 0.6, "weight": 0.8 }
}
}
EOF
Step 1.1: Analyze Existing Documentation Structure
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 · 807 lines · 0 tokens per session scan C 0b60e243ccf2
docs-improvement-game is a command published in the GitHub repository glassBead-tc/widescreen-research (6 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,162 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.