Cost Estimate

Estimate what it would cost a competent team to build, replace, or meaningfully advance the current codebase. Produce a professional report grounded in measured repository facts, explicit assumptions, and current market rates.

Core Rules

Stay Generic

• Analyze the actual repository instead of assuming a specific stack, language, or company shape.
• Use the file-reading, search, counting, git, and web-research tools available in the current agent environment. Do not depend on tool names from a single platform.
• Support repositories built mainly by humans, mainly by AI agents, or a mix of both.

Separate Facts From Inference

• Distinguish measured facts from judgment calls.
• Exclude obvious vendor code, generated artifacts, caches, lockfiles, build outputs, and bundled dependencies from primary LOC counts unless the user explicitly wants them included.
• Report uncertainty with ranges and a confidence level instead of pretending the estimate is precise.

Workflow