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

cc-codeconductor

v0.2.9

Published

A multi-agent orchestration framework for AI-assisted software engineering workflows.

Readme

CodeConductor

Stop prompting. Start orchestrating.

CodeConductor is an open-source framework for building structured, reproducible AI-assisted software engineering workflows.

It helps developers and teams coordinate specialized agents for planning, implementation, testing, documentation, and review — using versioned agent contracts, task cards, and risk-based routing.

[!IMPORTANT]

Current Scope

What works today:

  • npx cc-codeconductor init — detects project stack, writes .codeconductor/config.yml, copies council.yml and policy.yml into .codeconductor/presets/
  • npx cc-codeconductor install council --target <opencode|claude|codex|all> — generates and writes preset files; supports --global to install to ~/.opencode/, ~/.claude/, ~/.codex/
  • npx cc-codeconductor install lsp --target <opencode|claude|codex|gemini|cursor|agy|all> — installs LSP servers and configures AI coding tools; auto-detects project languages or use --lang to override
  • npx cc-codeconductor detect — detects project stack and recommends presets
  • npx cc-codeconductor doctor — validates configuration and installed runner directories
  • npx cc-codeconductor update — re-applies the council preset for the configured target
  • npx cc-codeconductor seo audit --url <url> — runs a comprehensive SEO audit on a single page (meta tags, schema.org, GEO readiness) and generates a markdown report
  • npx cc-codeconductor seo audit --sitemap <url> — batch audits all URLs from a sitemap.xml with rate limiting and SSRF prevention
  • npx cc-codeconductor seo llms --sitemap <url> — generates a llms.txt file for AI-search readiness from sitemap content
  • Manual presets for OpenCode, Claude Code, and Codex
  • Versioned Agent Contracts
  • Routing Policy documentation
  • Task Card, Scorecard, and workflow templates
  • Spring Boot/Kotlin and Python/Django workflow guidance

What does not exist yet:

  • Runtime sandbox enforcement
  • Policy compiler
  • Automated agent evaluation
  • Safe Merger
  • Multi-target update (currently updates only the defaults.target runner)

Security note:

CodeConductor currently provides declarative policies and documented guardrails. It does not yet enforce OS-level isolation, shell sandboxing, or runtime permission boundaries by itself. Treat all agent execution as dependent on the capabilities and limitations of the target tool.


Why CodeConductor?

Most AI coding workflows fail because they treat the model as a developer.

CodeConductor treats models as specialized workers inside a controlled engineering system. It defines:

  • who plans
  • who implements
  • who tests
  • who reviews
  • when to escalate
  • when to stop
  • how agent contracts evolve over time

This is not a prompt collection. It is a workflow framework.


Core Concepts

| Concept | Name in CodeConductor | | ------------------ | --------------------- | | Structured request | Task Card | | Flow decision | Route | | Specialized agent | Conductor Agent | | Decision rules | Routing Policy | | Versioned prompts | Agent Contracts | | Reusable knowledge | Skills | | Evaluable output | Deliverable | | Agent metrics | Scorecard |


How It Works

Task Card → Risk Classification → Routing Policy → Conductor Agent → Deliverable → Scorecard
  1. Define the task using a structured Task Card
  2. Classify risk (low / medium / high)
  3. Route to the correct Conductor Agent
  4. Implement with constraints
  5. Validate with tests
  6. Review before merge

Current Support (v0.2.0)

  • OpenCode preset
  • Claude Code-compatible preset
  • Codex preset
  • Spring Boot / Kotlin workflow
  • Python / Django workflow guidance
  • 8 core Conductor Agents
  • Routing Policy v0.1.0
  • Task Card template
  • Scorecard template
  • End-to-end example
  • YAML-driven model configuration

CLI Usage

Install

# Requires Bun ≥1.0 or Node ≥20.11
bun run src/cli/main.ts --help
# or after build:
# node dist/index.js --help

Commands

init — initialize CodeConductor in a project

npx cc-codeconductor init              # detect stack, write .codeconductor/config.yml
npx cc-codeconductor init --force      # overwrite existing config
npx cc-codeconductor init --global     # write to ~/.codeconductor/
npx cc-codeconductor init --dry-run    # preview without writing

On first run, init copies council.yml and policy.yml into .codeconductor/presets/ so you can customize them without touching framework files. install reads from there first.

detect — detect project stack

npx cc-codeconductor detect
npx cc-codeconductor detect --output json

Output:

Detected:
  - languages: javascript, typescript
  - runtimes: node, bun
  - frameworks: ...

install — install council preset

npx cc-codeconductor install council --target opencode     # project-level
npx cc-codeconductor install council --target claude
npx cc-codeconductor install council --target codex
npx cc-codeconductor install council --target all          # all three targets

npx cc-codeconductor install council --target claude --global  # write to ~/.claude/
npx cc-codeconductor install council --target opencode --global
npx cc-codeconductor install council --target all --global

npx cc-codeconductor install council --target opencode --dry-run   # preview
npx cc-codeconductor install council --target opencode --force     # overwrite

Files generated per target:

| Target | Files written | | ---------- | ---------------------------------------------------------------- | | opencode | .opencode/commands/cc-council.md, .opencode/agents/council-*.md | | claude | .claude/skills/council/SKILL.md, .claude/agents/council-*.md | | codex | .codex/config.toml, .codex/agents/council_*.toml |

With --global, the same files are written under ~/ instead of ./.

install lsp — install and configure LSP servers

npx cc-codeconductor install lsp --target opencode          # auto-detect languages
npx cc-codeconductor install lsp --target all               # all AI tools
npx cc-codeconductor install lsp --target claude --lang typescript,python  # explicit languages
npx cc-codeconductor install lsp --target all --global      # global install + global configs
npx cc-codeconductor install lsp --target cursor --dry-run  # preview
npx cc-codeconductor install lsp --target all --force       # overwrite existing configs

Supported languages: TypeScript, PHP, Python via Pyright, Kotlin. Supported targets: opencode, claude, codex, gemini, cursor, agy.

doctor — validate configuration

npx cc-codeconductor doctor

Checks config exists and is valid, reports runner directory status.

update — re-apply preset

npx cc-codeconductor update
npx cc-codeconductor update --force
npx cc-codeconductor update --dry-run

Re-generates preset files for the defaults.target in your config.

Global options

| Flag | Description | | --------------- | ---------------------------------------- | | --force | Overwrite existing files | | --dry-run | Preview actions without writing | | --global | Target home directory instead of project | | --output json | Machine-readable JSON output |

Config directory

init creates .codeconductor/:

.codeconductor/
├── config.yml          # project settings, target, preset versions
└── presets/
    ├── council.yml     # customizable copy of the council preset
    └── policy.yml      # customizable copy of policy rules

Edit .codeconductor/presets/council.yml to add, remove, or reconfigure agents before running install.

Model Configuration

Each preset includes a YAML configuration file in src/presets/models/ that defines which models are used for each agent role:

src/presets/models/
├── opencode.yml    # model defaults for OpenCode target
├── claude.yml      # model defaults for Claude target
└── codex.yml       # model defaults for Codex target

Agent template files contain placeholders that are replaced during install:

| Placeholder | Description | | -------------------- | ------------------------------- | | {{MODEL_CLAUDE}} | Model for the Claude provider | | {{MODEL_OPENCODE}} | Model for the OpenCode provider | | {{MODEL_CODEX}} | Model for the Codex provider |

To customize models, edit the YAML file for your target before running install. Each file maps agent roles to provider-specific model names.


Repository Structure

codeconductor/
├── README.md
├── LICENSE
├── CHANGELOG.md
├── ROADMAP.md
├── SECURITY.md
├── policy.yml              ← declarative policy model
│
├── src/                    ← CLI source (TypeScript + Bun)
│   ├── cli/                ← entry point, router, error codes
│   ├── commands/           ← init, detect, install, doctor, update
│   ├── core/               ← config, detection, filesystem, presets
│   ├── adapters/           ← opencode, claude, codex generators
│   ├── domain/council/     ← council spec, agent, contract
│   ├── validation/         ← Zod schemas
│   ├── utils/              ← Result type, logger, invariant
│   └── presets/council/    ← bundled council.yml preset
│
├── test/
│   ├── cli.test.ts         ← integration tests (32 tests)
│   └── fixtures/           ← bun, node, django, spring projects
│
├── docs/
│   ├── architecture.md
│   ├── security-model.md
│   ├── cli-contract.md
│   ├── policy-schema.md
│   ├── routing-policy.md
│   ├── task-card-template.md
│   ├── agent-scorecard.md
│   └── guides/
│
├── presets/                ← manual preset files (pre-CLI)
│   ├── opencode/
│   └── claude/
│
└── examples/
    └── spring-boot-kotlin/

Roadmap

| Version | Focus | | ---------- | ----------------------------------------------------------- | | v0.2.0 | CLI: init, detect, install, doctor, update — shipped ✅ | | v0.3.0 | Next.js, FastAPI, generic presets, monorepo support | | v0.4.0 | Provider compatibility matrix and target sync workflows | | v0.5.0 | Scorecard CLI, task outcome tracking, prompt regression | | v1.0.0 | Stable contracts, stable routing, documented evaluation |

See ROADMAP.md for details.


Contributing

See CONTRIBUTING.md.


License

MIT — see LICENSE.