npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

codex-command-suite

v1.0.1

Published

Intelligent code automation core with a safe automation command suite.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

prodigitalhubworldwideprodigitalhubworldwide

Keywords

Readme

Codex Command Suite

codex-command-suite is a local-first TypeScript CLI for features 1 through 10 of the project roadmap. The main entrypoint is codex-core.

Setup

npm install
npm run build
npm run test
npm run lint

Point 10 environment scaffolding:

copy point10.example.env .env

For source execution without a global install, use:

npm exec tsx -- src/index.ts --help
npm exec tsx -- src/index.ts automation --help
node dist/src/index.js --help

Shared Behavior

  • Inputs are validated with Zod before execution.
  • Write-capable commands default to preview mode unless --write is passed.
  • Structured logs are emitted to stderr.
  • Command families surface typed errors.
  • Retryable operations are retried once.
  • Many commands support --report text or --report json.

Command Reference

Automation

codex-core automation suggest

  • Purpose: generate an implementation suggestion from a goal and optional context files.
  • Options: --goal <goal>, --context <file...>.
  • Example: codex-core automation suggest --goal "extract validation into a shared schema module" --context src/index.ts

codex-core automation patch

  • Purpose: preview or apply a generated patch block to a target file.
  • Options: --target <file>, --goal <goal>, --anchor <text>, --dry-run, --write.
  • Examples:
codex-core automation patch --target src/index.ts --goal "add startup logging" --dry-run
codex-core automation patch --target src/index.ts --goal "add startup logging" --write

codex-core automation debug

  • Purpose: produce a probable diagnosis and remediation path for an error.
  • Options: --error <message>, --context <file...>.
  • Example: codex-core automation debug --error "TypeError: Cannot read properties of undefined" --context src/services/automation/intelligence-service.ts

codex-core automation test-gen

  • Purpose: preview or write a generated test scaffold for a source file.
  • Options: --target <file>, --output <file>, --style <style>, --dry-run, --write.
  • Examples:
codex-core automation test-gen --target src/services/automation/intelligence-service.ts --dry-run
codex-core automation test-gen --target src/services/automation/intelligence-service.ts --output tests/generated/intelligence-service.test.ts --write

codex-core automation doc-sync

  • Purpose: preview or write documentation generated from source files.
  • Options: --source <file...>, --doc <file>, --dry-run, --write.
  • Examples:
codex-core automation doc-sync --source src/index.ts --source src/cli/commands/automation.ts --dry-run
codex-core automation doc-sync --source src/index.ts --source src/cli/commands/automation.ts --doc docs/AUTOMATION_COMMAND_SUITE.md --write

Agent

codex-core agent start

  • Purpose: start a bounded agent workflow and persist its state.
  • Options: --task <task>, --risk <level>, --budget <count>, --depth <count>, --storage <dir>, --memory.
  • Example: codex-core agent start --task "review, implement, and verify the CLI update" --risk low --budget 4 --depth 2

codex-core agent resume

  • Purpose: resume a persisted agent workflow.
  • Options: --agent-id <id>, --budget <count>, --depth <count>, --storage <dir>.
  • Example: codex-core agent resume --agent-id agent-123 --budget 3 --depth 2

codex-core agent status

  • Purpose: inspect agent state, memory, and checkpoint progress.
  • Options: --agent-id <id>, --storage <dir>.
  • Example: codex-core agent status --agent-id agent-123

codex-core agent stop

  • Purpose: stop a running agent and persist a final checkpoint.
  • Options: --agent-id <id>, --reason <text>, --storage <dir>.
  • Example: codex-core agent stop --agent-id agent-123 --reason "budget exhausted, waiting for operator review"

DevOps

codex-core devops ci-check

  • Purpose: inspect repository workflows and generate CI recommendations.
  • Options: --repo <path>.
  • Example: codex-core devops ci-check --repo .

codex-core devops pr-review

  • Purpose: generate a repository-aware PR review summary.
  • Options: --title <title>, --summary <summary>, --branch <branch>, --changed <file...>, --diff <path>, --repo <path>.
  • Example: codex-core devops pr-review --title "feat: add deploy workflows" --summary "Adds deployment planning and rollback planning commands." --branch feat/devops --changed src/cli/commands/devops.ts .github/workflows/ci.yml

codex-core devops deploy-plan

  • Purpose: generate a deployment plan from detected repository workflows.
  • Options: --change <description>, --environment <name>, --repo <path>.
  • Example: codex-core devops deploy-plan --environment production --change "Promote feature 3 after CI passes"

codex-core devops rollback-plan

  • Purpose: generate a rollback procedure from detected repository workflows.
  • Options: --incident <description>, --environment <name>, --repo <path>.
  • Example: codex-core devops rollback-plan --environment production --incident "Release caused elevated error rates"

Security And Audit

codex-core audit --security

  • Purpose: run repository security audit workflows.
  • Options: --security, --repo <path>, --report <format>.
  • Example: codex-core audit --security --repo .

codex-core secrets-scan

  • Purpose: scan files for common secret patterns without modifying anything.
  • Options: --repo <path>, --files <file...>, --allowlist <file...>, --suppress <entry...>, --report <format>.
  • Example: codex-core secrets-scan --repo . --files .env package.json README.md --suppress .env

codex-core compliance

  • Purpose: generate a basic security compliance checklist.
  • Options: --repo <path>, --standard <name>, --report <format>.
  • Example: codex-core compliance --repo . --standard soc2-lite

codex-core sandbox-run

  • Purpose: preview or run an allowlisted command in an isolated subprocess.
  • Options: --cmd <command>, --arg <arg...>, --allow-command <command...>, --cwd <path>, --timeout <ms>, --dry-run, --write, --report <format>.
  • Examples:
codex-core sandbox-run --cmd node --arg=--version --dry-run
codex-core sandbox-run --cmd node --arg=--version --write

Finance

codex-core finance cost-estimate

  • Purpose: estimate rough monthly development infrastructure costs.
  • Options: --repo <path>, --environment <name>, --engineers <count>, --services <count>, --ci-runs <count>, --service-cost <usd>, --ci-run-cost <usd>, --engineer-tooling-cost <usd>, --report <format>, --report-file <path>.
  • Examples:
codex-core finance cost-estimate --environment dev --engineers 4 --services 6
codex-core finance cost-estimate --environment staging --service-cost 60 --report json --report-file reports/cost-estimate.json

codex-core finance optimize --cloud

  • Purpose: generate cloud-cost optimization suggestions.
  • Options: --cloud, --repo <path>, --environment <name>, --budget <usd>, --shutdown-rate <ratio>, --reserved-rate <ratio>, --storage-rate <ratio>, --report <format>, --report-file <path>.
  • Examples:
codex-core finance optimize --cloud --environment production --budget 1500
codex-core finance optimize --cloud --environment dev --budget 500 --shutdown-rate 0.25 --reserved-rate 0.15

codex-core finance token-efficiency

  • Purpose: generate token budgeting placeholders and efficiency suggestions.
  • Options: --repo <path>, --monthly-tokens <count>, --avg-prompt <count>, --avg-completion <count>, --prompt-savings <usd>, --completion-savings <usd>, --report <format>, --report-file <path>.
  • Examples:
codex-core finance token-efficiency --monthly-tokens 2000000 --avg-prompt 3500 --avg-completion 1200
codex-core finance token-efficiency --monthly-tokens 1500000 --prompt-savings 50 --completion-savings 15 --report json

codex-core finance usage-analytics

  • Purpose: read local development cost and usage metrics.
  • Options: --repo <path>, --window-days <days>, --storage <path>, --report <format>, --report-file <path>.
  • Examples:
codex-core finance usage-analytics --window-days 30
codex-core finance usage-analytics --report json --report-file reports/usage.json

Product

codex-core product scaffold --startup

  • Purpose: preview or generate a startup-oriented application skeleton.
  • Options: --startup, --name <name>, --target <path>, --product-type <type>, --audience <audience>, --report <format>, --dry-run, --write.
  • Examples:
codex-core product scaffold --startup --name PulseDesk --dry-run
codex-core product scaffold --startup --name PulseDesk --product-type saas --audience b2b --target generated/pulsedesk --write

codex-core product landing-gen

  • Purpose: preview or generate a landing page asset pack.
  • Options: --name <name>, --tagline <tagline>, --audience <audience>, --tone <tone>, --output <path>, --report <format>, --dry-run, --write.
  • Examples:
codex-core product landing-gen --name PulseDesk --tagline "Run operations without spreadsheet drag" --dry-run
codex-core product landing-gen --name PulseDesk --tagline "Run operations without spreadsheet drag" --audience b2b --write

codex-core product seo-optimize

  • Purpose: generate SEO recommendations from local repository signals.
  • Options: --repo <path>, --domain <domain>, --page <name>, --keyword <value...>, --report <format>.
  • Examples:
codex-core product seo-optimize --repo . --page landing --keyword operations --keyword automation
codex-core product seo-optimize --repo . --domain example.com --page pricing --report json

codex-core product monetization-suggest

  • Purpose: generate monetization suggestions from product type and stage.
  • Options: --repo <path>, --product-type <type>, --audience <audience>, --stage <stage>, --target-price <usd>, --report <format>.
  • Examples:
codex-core product monetization-suggest --product-type ai-app --audience b2b --stage mvp --target-price 79
codex-core product monetization-suggest --product-type developer-tool --audience developer --stage growth --report json

Context Intelligence

codex-core context-map

  • Purpose: build a local repository context graph from files, docs, and dependency edges.
  • Options: --repo <path>, --storage <path>, --ignore <pattern...>, --max-files <count>, --no-incremental, --report <format>.
  • Example: codex-core context-map --repo .

codex-core repo-index

  • Purpose: index repository files and dependency edges into local context storage.
  • Options: --repo <path>, --storage <path>, --ignore <pattern...>, --max-files <count>, --no-incremental, --report <format>.
  • Example: codex-core repo-index --repo .

codex-core docs-index

  • Purpose: index markdown documentation into local context storage.
  • Options: --repo <path>, --storage <path>, --ignore <pattern...>, --max-files <count>, --no-incremental, --report <format>.
  • Example: codex-core docs-index --repo .

codex-core cross-repo-plan

  • Purpose: plan a coordinated change across multiple locally indexed repositories.
  • Options: --repos <path...>, --change <description>, --storage <path>, --report <format>.
  • Example: codex-core cross-repo-plan --repos . ../shared-lib --change "rename the automation result envelope"

UX

codex-core ux autocomplete

  • Purpose: generate shell autocomplete hooks with repo-aware command suggestions.
  • Aliases: codex-core ui autocomplete, codex-core ux ac.
  • Options: --repo <path>, --storage <path>, --shell <name>, --report <format>.
  • Examples:
codex-core ux autocomplete --shell powershell
codex-core ux autocomplete --shell bash --report shell

codex-core ux history

  • Purpose: view semantic UX history with optional intent filtering.
  • Aliases: codex-core ux hist.
  • Options: --storage <path>, --intent <name>, --limit <count>, --report <format>.
  • Examples:
codex-core ux history --limit 15
codex-core ux history --intent diff --report json

codex-core ux chat

  • Purpose: run a local chat-style planning interaction with session persistence.
  • Aliases: codex-core ux c.
  • Options: --message <text>, --repo <path>, --storage <path>, --session <name>, --report <format>.
  • Examples:
codex-core ux chat --message "what should I inspect before changing deploy flow?"
codex-core ux chat --session release-planning --message "summarize current production risks" --report json

codex-core ux diff

  • Purpose: render a rich terminal diff between two files.
  • Aliases: codex-core ux d.
  • Options: --before <file>, --after <file>, --context <count>, --report <format>.
  • Examples:
codex-core ux diff --before README.md --after docs/CONTEXT_INTELLIGENCE.md
codex-core ux diff --before src/index.ts --after dist/src/index.js --context 1 --report json

codex-core ux metrics

  • Purpose: show local command, repository, and storage metrics.
  • Aliases: codex-core ux m.
  • Options: --repo <path>, --storage <path>, --report <format>.
  • Examples:
codex-core ux metrics --repo .
codex-core ux metrics --storage .codex-core/ux --report json

codex-core ux risk-summary

  • Purpose: summarize risk for a proposed change with simple mitigations.
  • Aliases: codex-core ux risk.
  • Options: --change <text>, --repo <path>, --storage <path>, --confirm, --yes, --report <format>.
  • Examples:
codex-core ux risk-summary --change "deploy authentication changes to production"
codex-core ux risk-summary --change "rotate plugin registry format" --confirm

Plugin

codex-core plugin create

  • Purpose: preview or create a local plugin scaffold.
  • Options: --name <name>, --target <path>, --report <format>, --dry-run, --write.
  • Examples:
codex-core plugin create --name sample-plugin --dry-run
codex-core plugin create --name sample-plugin --target plugins --write

codex-core plugin install

  • Purpose: install a local plugin into the plugin registry.
  • Options: --source <path>, --registry <path>, --report <format>.
  • Examples:
codex-core plugin install --source plugins/sample-plugin
codex-core plugin install --source plugins/sample-plugin --registry .codex-core/plugins --report json

codex-core plugin list

  • Purpose: list locally installed plugins.
  • Options: --registry <path>, --report <format>.
  • Examples:
codex-core plugin list
codex-core plugin list --registry .codex-core/plugins --report json

codex-core plugin remove

  • Purpose: remove an installed plugin from the local registry.
  • Options: --name <name>, --registry <path>, --report <format>.
  • Examples:
codex-core plugin remove --name sample-plugin
codex-core plugin remove --name sample-plugin --registry .codex-core/plugins

codex-core plugin run

  • Purpose: run an installed plugin command or lifecycle entrypoint.
  • Options: --name <name>, --command <name>, --arg <value...>, --registry <path>, --report <format>.
  • Examples:
codex-core plugin run --name sample-plugin --command hello --arg world
codex-core plugin run --name sample-plugin --command main --report json

Point 10 Strategic Modes

codex-core point10 plan

  • Purpose: build a strategic plan for one of the three point 10 modes using the checkpoint contract and current local signals.
  • Options: --mode <mode>, --goal <text>, --repo <path>, --repos <path...>, --success-metric <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 plan --mode autonomous-cto --goal "Ship a safer weekly release process"

codex-core point10 run

  • Purpose: execute a bounded strategic run with persistent point 10 state.
  • Options: --mode <mode>, --goal <text>, --monthly-revenue-target <usd>, --baseline-score <score>, --target-score <score>, --storage <path>, --report <format>, --dry-run, --write.
  • Examples:
codex-core point10 run --mode revenue-driven-coding --goal "Increase MRR with better acquisition and pricing" --monthly-revenue-target 25000
codex-core point10 run --mode self-improving-system --target-score 90 --write

codex-core point10 status

  • Purpose: inspect the persisted point 10 state and last plan/evaluation.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 status

codex-core point10 eval

  • Purpose: evaluate the active point 10 mode against baseline and target scores.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 eval --report json

codex-core point10 stop

  • Purpose: stop the active point 10 mode and persist the operator reason.
  • Options: --storage <path>, --reason <text>, --report <format>.
  • Example: codex-core point10 stop --reason "operator requested stop"

codex-core point10 cto backlog

  • Purpose: prioritize a bounded Autonomous CTO backlog using checkpoint decision inputs and local repo signals.
  • Options: --goal <text>, --item <title|domain|impact|effort|risk|urgency|notes>, --top-business-objective <text>, --top-technical-objective <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 cto backlog --item "Stabilize CI|delivery|5|2|2|5|Tighten release confidence"

codex-core point10 cto tech-plan

  • Purpose: create a bounded technical plan with workstreams, phases, dependencies, and command recommendations.
  • Options: --initiative <text>, --goal <text>, --release-horizon <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 cto tech-plan --initiative "Weekly release hardening"

codex-core point10 cto architecture

  • Purpose: produce architecture recommendations aligned to release safety, compliance, and architectural churn tolerance.
  • Options: --initiative <text>, --acceptable-architectural-churn <level>, --required-compliance-level <level>, --storage <path>, --report <format>.
  • Example: codex-core point10 cto architecture --initiative "Plugin runtime isolation"

codex-core point10 cto sequence

  • Purpose: generate an implementation sequence that stays within the current risk and cadence envelope.
  • Options: --initiative <text>, --item <title|domain|impact|effort|risk|urgency|notes>, --shipping-cadence-target <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 cto sequence --initiative "Release control plane"

codex-core point10 cto memory

  • Purpose: inspect or append bounded Autonomous CTO strategic memory.
  • Options: --remember <text>, --category <type>, --storage <path>, --report <format>.
  • Example: codex-core point10 cto memory --remember "Release safety outranks plugin expansion" --category decision

codex-core point10 cto status

  • Purpose: inspect the latest Autonomous CTO artifacts and memory state.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 cto status

codex-core point10 cto run

  • Purpose: execute the full Autonomous CTO recommendation pipeline within the checkpoint safety contract.
  • Options: --goal <text>, --initiative <text>, --item <title|domain|impact|effort|risk|urgency|notes>, --storage <path>, --report <format>, --dry-run, --write.
  • Example: codex-core point10 cto run --goal "Ship a safer weekly release process" --initiative "Release control plane"

codex-core point10 revenue analyze

  • Purpose: attach business impact analysis to a proposed feature, including revenue levers, conversion implications, monetization path, effort, and confidence.
  • Options: --feature <title|summary|area|userValue|engineeringScope|lever1,lever2|dep1,dep2>, --target-audience <text>, --primary-monetization-model <model>, --price-target <usd>, --report <format>.
  • Example: codex-core point10 revenue analyze --feature "Improve onboarding|Reduce time-to-value|activation|5|medium|activation,conversion|analytics"

codex-core point10 revenue portfolio

  • Purpose: rank multiple features by business score relative to estimated engineering effort.
  • Options: --feature <title|summary|area|userValue|engineeringScope|lever1,lever2|dep1,dep2>, --goal <text>, --target-audience <text>, --conversion-target <ratio>, --report <format>.
  • Example: codex-core point10 revenue portfolio --goal "Increase paid conversion"

codex-core point10 revenue map

  • Purpose: generate a structured mapping from code workstreams to business outcomes and revenue levers.
  • Options: --feature <title|summary|area|userValue|engineeringScope|lever1,lever2|dep1,dep2>, --target-audience <text>, --primary-monetization-model <model>, --report <format>.
  • Example: codex-core point10 revenue map --feature "Pricing comparison|Clarify plan limits|pricing|4|small|conversion,expansion|pricing page"

codex-core point10 revenue compare

  • Purpose: compare conservative, base, and optimistic revenue scenarios for a feature with capped heuristic estimates.
  • Options: --feature <...>, --assumption <key=value>, --profile <name>, --scenarios <name...>, --report <format>.
  • Example: codex-core point10 revenue compare --feature "Improve onboarding|Reduce time-to-value|activation|5|medium|activation,conversion|analytics"

codex-core point10 revenue profile

  • Purpose: load or edit a named revenue business input profile.
  • Options: --name <text>, --set <key=value>, --storage <path>, --report <format>.
  • Example: codex-core point10 revenue profile --name growth-default --set decisionInputs.targetAudience=developer --set assumptions.reachableAudienceSize=800

codex-core point10 revenue status

  • Purpose: inspect the latest revenue-driven coding artifacts and state.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 revenue status

codex-core point10 revenue run

  • Purpose: execute the full revenue-driven analysis pipeline and map code work to business outcomes.
  • Options: --goal <text>, --feature <title|summary|area|userValue|engineeringScope|lever1,lever2|dep1,dep2>, --storage <path>, --report <format>, --dry-run, --write.
  • Example: codex-core point10 revenue run --goal "Increase paid conversion" --report json

codex-core point10 self outcome

  • Purpose: store an outcome summary from a prior run for later learning analysis.
  • Options: --summary <text>, --status <level>, --impact <level>, --source <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 self outcome --summary "Prompt failed to isolate the test target" --status negative

codex-core point10 self learn

  • Purpose: generate a bounded learning summary from prior outcomes and local run artifacts.
  • Options: --baseline-performance-score <score>, --target-improvement-score <score>, --evaluation-window <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 self learn

codex-core point10 self errors

  • Purpose: track recurring errors from stored outcomes and bounded runtime signals.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 self errors

codex-core point10 self prompt-effectiveness

  • Purpose: measure prompt effectiveness from semantic history without auto-modifying prompt sources.
  • Options: --storage <path>, --ux-storage <path>, --report <format>.
  • Example: codex-core point10 self prompt-effectiveness

codex-core point10 self recommend

  • Purpose: recommend bounded strategy adjustments for future plans.
  • Options: --allowed-self-modification-surface <text>, --rollback-condition <text>, --stop-condition <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 self recommend

codex-core point10 self status

  • Purpose: inspect self-improving artifacts and state.
  • Options: --storage <path>, --report <format>.
  • Example: codex-core point10 self status

codex-core point10 self run

  • Purpose: execute the full self-improving analysis pipeline without leaving proposal-only safety boundaries.
  • Options: --storage <path>, --report <format>, --dry-run, --write.
  • Example: codex-core point10 self run --report json

codex-core point10 self rollback

  • Purpose: roll back the active self-improving strategy profile to a prior version.
  • Options: --target-version <text>, --storage <path>, --report <format>.
  • Example: codex-core point10 self rollback --target-version v123456789

Verification

npm run build
npm run test
npm run lint
npm run smoke
npm run smoke:automation
npm run smoke:agent
npm run smoke:devops
npm run smoke:security
npm run smoke:finance
npm run smoke:point10
npm run smoke:point10:cto
npm run smoke:point10:revenue
npm run smoke:point10:self
npm run smoke:product
npm run smoke:context
npm run smoke:ux
npm run smoke:plugin

Point 10 Configuration

Use point10.example.env as the starting template for point 10 runtime configuration. Use POINT10_DECISION_INPUTS_TEMPLATE.json when you want to feed a full validated decision-input set into the CLI with --decision-inputs-file. The full variable-by-variable reference, including defaults, allowed values, examples, and mode impact notes, is in docs/POINT10_ENV_REFERENCE.md.

Feature Docs

Release Docs