Skip to content

teterouge/codeworth

repo-estimator

Verified

Analyze a code repository and produce a detailed human time and cost estimate for building it from scratch. Use this skill whenever the user wants to know how long it would take a human developer or team to build a codebase, how much it would cost to recreate a project, what the engineering effort of a repo is, or wants a "what's this worth?" / "how much work went into this?" type of analysis. Also trigger for requests like "estimate this project", "how many dev hours is this", "what would it cost to build this", "audit this repo for effort", "scope this codebase", or any time someone shares a repo path or GitHub URL and asks about effort, time, team size, or cost. Even if they don't use the words "estimate" or "cost" — if they share code and ask about effort or what it would take to build, use this skill.

examples/sanitized-security-app-report.md

View on GitHub
# Example Codeworth Analysis Report

This is a **sanitized example** of a Codeworth repository estimation report.  
Details have been generalized to avoid exposing sensitive implementation specifics while preserving the reasoning and structure of the analysis.

---

# Repository Estimation Report

**Repository:** Android Security Application (sanitized example)  
**Analyzed:** 2026-03-08  
**Estimated for:** Small startup team (2–4 engineers + 1 PM)

---

# Executive Summary

The analyzed repository represents a specialized Android security application designed to maintain two independent operating environments on a single device.

The architecture relies heavily on Android platform internals and security-oriented design patterns. Although the codebase itself is modest in size (~22,000 lines of code), the repository encodes a substantial amount of domain expertise around:

- Android multi-user management
- system-level device administration APIs
- security-driven UX constraints
- failure-safe destructive operations
- covert activation flows
- threat-model-driven validation

Because of these characteristics, rebuild effort is dominated not by raw implementation work but by **research, threat modeling, and platform-specific engineering knowledge**.

A team unfamiliar with this domain would spend significant time understanding Android’s user isolation model, system APIs, and security constraints before implementing the system.

---

# High-Level Estimate

| Metric | Estimate |
|------|------|
| Estimated rebuild effort | **40–54 weeks** |
| Person-years | **~2.3 person-years** |
| Estimated cost range | **$350k – $640k USD** |
| Confidence | **Medium** |

Confidence is moderate because repository artifacts reveal architecture and documentation clearly, but ramp-up time for platform-specific expertise varies significantly across teams.

---

# Repository Overview

**Primary languages**

- Kotlin (Android application)
- TypeScript (marketing/website layer)

**Architecture**

- Multi-layered Android application
- Supporting web surface for documentation and provisioning
- Platform-integrated services and permission-controlled capabilities

**Approximate size**

~22,000 LOC excluding generated/vendor code

**Technology stack**

- Android SDK
- Kotlin
- Gradle build system
- Google Play Billing
- Next.js website layer
- analytics integrations

**Test coverage**

Minimal automated coverage:

- targeted unit tests for critical components
- performance benchmark for timing-sensitive flows

Security-critical logic is partially covered by tests but full system integration tests are limited.

---

# Rebuild Difficulty Assessment

**Overall rating:** HIGH

The repository scored highly in several categories that strongly affect rebuild effort.

### Domain Knowledge

The system requires specialized understanding of:

- Android device administration APIs
- secondary user management
- platform security boundaries
- adversarial UX scenarios
- failure-safe destructive operations

This knowledge is not widely distributed among typical mobile engineers.

### Integration Surface

The repository integrates with multiple Android subsystems:

- device administration APIs
- system services
- billing infrastructure
- cross-process communication
- background services

Several integrations rely on **underdocumented platform behaviors**.

### Operational Maturity

Although the application is small, the repository contains meaningful operational artifacts:

- validation documentation
- structured logging
- performance benchmarks
- specification documents
- security design notes

These artifacts signal a product built with deliberate validation and threat modeling.

---

# Component Breakdown (Engineering)

| Component | Complexity Tier | Notes |
|---|---|---|
| Core security engine | Tier 4 | Security-critical logic controlling destructive operations |
| Profile / environment management | Tier 4 | Deep integration with Android multi-user system |
| Entitlement & authority service | Tier 3–4 | Cross-process service architecture |
| Billing integration | Tier 2–3 | Subscription flow and entitlement management |
| Disguise / activation system | Tier 3 | Platform-level application alias manipulation |
| Policy enforcement modules | Tier 3 | Runtime system behavior enforcement |
| UI layer | Tier 2 | Multiple flows and configuration screens |
| Android service integrations | Tier 3 | Accessibility, admin services, background processes |
| Data layer | Tier 2 | Secure local storage |
| Test suite | Tier 3 | Security-critical validation tests |
| Website surface | Tier 1–2 | Marketing and provisioning pages |
| Build & configuration | Tier 1–2 | Android build system configuration |

Total engineering effort (after complexity adjustments):

**~2,240 hours**

---

# Engineering Adjustment Factors

Engineering effort must account for additional realities of real-world development.

| Factor | Adjustment |
|---|---|
| Iteration and rework | +50% |
| Testing and QA | +15% |
| Documentation overhead | +10% |
| Team coordination | +10% |
| Integration complexity | +15% |

Engineering subtotal after adjustments:

**~2,240 hours**

---

# Product Management Effort

The repository contains strong signals of significant product management effort.

Artifacts observed include:

- detailed specification documents
- feature breakdowns
- phase-based development documentation
- acceptance test criteria
- validation results
- threat model documentation

Estimated PM effort:

**~470 hours**

Major PM activities included:

| Activity | Estimated Hours |
|---|---|
| User research and threat modeling | 80 |
| Feature specification | 220 |
| Roadmap and planning | 55 |
| Validation and release coordination | 75 |
| Iteration and post-launch analysis | 40 |

PM effort represents approximately **21% of engineering effort**, which is typical for complex consumer security products.

---

# Recommended Team Composition

A typical rebuild would involve:

**Senior Android Engineer**

Primary owner of platform integration and security-critical systems.

**Mid-Level Android / Full Stack Engineer**

Responsible for UI flows, integrations, and supporting systems.

**Product Manager / Security-Oriented PM**

Responsible for threat model translation, feature specification, and validation coordination.

A single senior engineer could build the system alone but would likely need to assume product responsibilities as well.

---

# Estimated Timeline

| Scenario | Timeline |
|---|---|
| Aggressive | ~8 months |
| Realistic | ~10 months |
| Conservative | ~13 months |

Ramp-up time for engineers unfamiliar with Android system APIs is the primary timeline risk.

---

# Unified Cost Estimate

Assuming US-market engineering rates:

| Scenario | Total Hours | Estimated Cost |
|---|---|---|
| Low | ~2,740 hrs | ~$350k |
| Mid | ~3,660 hrs | ~$480k |
| High | ~4,940 hrs | ~$640k |

---

# Key Complexity Drivers

Several factors materially increased rebuild difficulty:

**Platform-specific engineering**

The architecture depends heavily on Android platform behaviors that are poorly documented.

**Security-driven product design**

Correctness requirements include:

- adversarial scenario handling
- failure-safe destructive operations
- strict behavioral guarantees

These constraints raise implementation difficulty significantly.

**Embedded product knowledge**

The repository contains substantial design reasoning encoded in specifications, validation artifacts, and system architecture.

---

# Caveats and Assumptions

The analysis assumes:

- the rebuilding team does not already possess deep platform expertise
- the repository reflects the final production architecture
- implementation must meet similar security guarantees

The estimate excludes:

- UI design work
- legal review
- security audits
- operational infrastructure costs

These could add **$40k–$100k+** depending on scope.

---

# Key Insight

The analyzed repository demonstrates a common pattern:

A codebase may appear small in raw LOC but still represent **hundreds of thousands of dollars in engineering effort** because the real asset lies in **embedded domain knowledge and system design decisions**.

Codeworth is designed to surface this hidden replacement cost.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall