10-optimization-finalization

A release-preparation workflow that reviews a software project from several specialist angles before it is put into production, meaning made available for real users.

In plain words
What is it for?
Use it to improve a product requirements document, consolidate documentation, find code and security issues, plan a release, and prepare the system for production.
Why use it?
It brings architecture, performance, quality, security, planning, and documentation checks into one final review.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/clchinkc/document-mcp/10-optimization-finalization
Clone the repo
git clone --depth 1 https://github.com/clchinkc/document-mcp

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 626 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00626
Opus 5 $0.00000 $0.00313
Sonnet 5 $0.00000 $0.00125
Haiku 4.5 $0.00000 $0.00063

Measured yesterday against content hash 1bc4b9581d15, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

10-optimization-finalization 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 yesterday.

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.

.claude/commands/10-optimization-finalization.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

System Optimization & Release Finalization

Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.

Phase 1: Multi-Agent Optimization Round Robin

Use diverse specialized agents for comprehensive system optimization:

Architecture & Performance:

  • Backend Architect: System design optimization, service architecture, API design
  • Performance Optimizer: Performance bottlenecks, caching strategies, resource optimization
  • Frontend System Builder: UI/UX optimization, component architecture, user experience
  • AI Engineer: ML/AI system optimization, model performance, intelligent features

Quality & Security:

  • QA Engineer: Quality assurance processes, testing optimization, defect prevention
  • Security Auditor: Security hardening, vulnerability assessment, privacy compliance
  • Code Refactoring Specialist: Code quality, maintainability, architectural improvements

Planning & Documentation:

  • Behavior Analyst: User behavior analysis, requirement validation, scenario optimization
  • Sprint Prioritizer: Feature prioritization, release planning, roadmap optimization

Phase 2: PRD & Documentation Enhancement

PRD Improvement Process:

  • Research current documentation and integrate insights organically, logically, naturally
  • Ultrathink critique, evaluate, and discuss structural improvements
  • Keep organization coherent and logical with concise formatting
  • Maintain original wording and content details while improving information density
  • Output everything in English with ALL existing details preserved
  • Keep remaining content in original language where specified

Documentation Consolidation:

  • Consolidate all recent modifications into current status sections
  • Eliminate "recent modification" sections - integrate changes organically
  • Update all documentation based on system modifications
  • Ensure documentation accuracy reflects actual implementation
  • Prepare documentation for production release

Read the full file on GitHub · 69 lines

Changes

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.

  1. yesterday First seen · 69 lines · 0 tokens per session scan A 1bc4b9581d15

Subscribe to this mod's changes

10-optimization-finalization is a command published in the GitHub repository clchinkc/document-mcp (0 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 626 tokens. 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.