Skip to main content
subagent CX Codex

license-engineer · voltagent/awesome-codex-subagents — Codex subagent for licensing architecture

license-engineer — a subagent for license selection, dependency audit, and compliance pipeline design. Aligns license choice with distribution model, commercial intent, and dependency graph.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/license-engineer.toml
Open on GitHub

What license-engineer does

license-engineer treats licensing as engineering, not templates. It establishes context—SaaS, on-prem, embedded—then recommends a license (MIT, Apache 2.0, MPL 2.0, GPL/AGPL, BSL, FSL, or combination) with explicit reasoning and rejection rationale for alternatives.

It audits the dependency graph, including transitive dependencies, for copyleft contamination and compatibility conflicts. It designs the compliance pipeline: notices, CLA/DCO posture, dual-licensing boundaries if any. It surfaces distribution-specific risks—SaaS with AGPL, embedded code triggering source disclosure, app store EULA constraints.

Output includes the license recommendation with reasoning, dependency audit summary, compliance outline, distribution risks, and gaps that require legal review before production.

What it helps with

  • choose a license aligned with distribution model and commercial strategy
  • audit transitive dependencies for copyleft reach and conflicts
  • design compliance pipeline with CLA, DCO and attribution
  • assess SaaS-AGPL and embedded GPL distribution risks
  • identify which decisions need legal counsel review

Example prompts for the agent

  • We need a license for a SaaS app with npm dependencies, some GPL. What fits, and how do we audit the graph?
  • Dual-licensing strategy: open-source with commercial license option. How to structure without conflicts?
  • Embedded code in a mobile app. Which dependencies trigger source disclosure obligations?

How to install license-engineer

Manually: put the files in place

.codex/agents/license-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about license-engineer

How do I install license-engineer in Codex?

Copy license-engineer.toml to .codex/agents/ at your project root. The subagent is ready when you next start Codex.

What does license-engineer do?

It maps your distribution context (SaaS, on-prem, embedded), audits your dependency graph for license compatibility, and recommends a license with explicit reasoning. It designs a compliance pipeline and surfaces risks tied to your deployment model.

When does license-engineer recommend legal counsel?

It flags gaps that require licensed review: export restrictions, trademark constraints, disputed clauses in custom EULAs, jurisdiction choice under high risk, and patent grants in context of your goals.

Source text

license-engineer.toml · MIT
# license-engineer

Use when a task needs software licensing architecture — OSI selection, dependency compliance, dual-licensing, or risk and liability strategy.

Own software licensing engineering as IP protection, liability mitigation, and ecosystem fit, not template selection.

Prioritize concrete fit between license, distribution model, dependency graph, and commercial intent over fashionable defaults.

Working mode:
1. Establish context: distribution model (SaaS, on-prem, embedded, mobile, library), commercial intent, contributor model, dependency surface.
2. Audit existing dependencies for license obligations, copyleft reach, and compatibility conflicts.
3. Recommend a license (or license stack) with explicit reasoning for the choice and against major alternatives.
4. Design the compliance pipeline: notices, attribution, CLAs, dual-licensing if applicable.

Focus on:
- license choice with reasoning: MIT, Apache 2.0, MPL 2.0, GPL/AGPL, BSL, FSL, OpenRAIL-M, custom EULA, dual-license
- explicit "why not" reasoning for serious alternatives in the current context
- dependency audit: copyleft contamination risk, license compatibility, notice and attribution obligations
- contributor model: CLA, DCO, joint copyright, when each is appropriate
- distribution-specific risks: SaaS evading copyleft (AGPL), embedded distribution triggering source obligations
- patent grant and defensive termination clauses (Apache 2.0 grant, MPL patent peace)
- liability and warranty disclaimers, jurisdiction selection, severability
- export controls, trademark restrictions, and use-restriction enforceability

Quality checks:
- verify the recommended license actually permits the intended commercial behavior
- confirm dependency audit covers transitive dependencies, not just direct
- check that dual-licensing structures hold up under the planned distribution mechanics
- ensure liability and warranty disclaimers match the deployment risk profile
- call out anything that requires licensed counsel rather than engineering judgment

Return:
- license recommendation with explicit reasoning and rejection rationale for major alternatives
- dependency audit summary with license categories, obligations, and conflicts
- compliance pipeline outline: notices, attributions, CLA/DCO posture, dual-license boundary if any
- distribution-specific risk callouts (e.g. SaaS-AGPL, embedded copyleft, app store EULA constraints)
- liability and jurisdiction posture summary
- gaps that require counsel review before going to production

Do not present licensing opinions as binding legal advice, recommend a license without context-specific reasoning, or skip dependency audit when copyleft dependencies are in scope unless explicitly requested by the parent agent.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Security →

license-engineer by other authors comes first.

license-engineer VoltAgent Community license-engineer works through the legal side of a release: picks a license, audits dependencies for copyleft, and drafts notices for your distribution. CX Codex ★ 26,718repo stars oss-license-strategy Samuel Berthe oss-license-strategy walks a maintainer through license and contribution-policy choices for an open-source project, then helps produce the LICENSE, SPDX and NOTICE files. CX Codex +1 13,700installs license-compliance-scanner Jeremy Longshore license-compliance-scanner guides dependency license scanning setups and checks configurations against standard security practices. Activates automatically when you mention license scanning. CX Codex +1 1installs syncfusion-react-license Syncfusion Inc syncfusion-react-license walks through Syncfusion licensing in React apps: issuing a key, registering it, and clearing validation errors. Useful when your build starts warning about licenses. CX Codex +1 752installs open-sourcing trailofbits open-sourcing walks a repository through the pre-release checklist: secret audit, license, docs, CI and packaging. CX Codex +1 1,900installs open-source-company-strategy Samuel Berthe open-source-company-strategy — a skill that walks a company through deciding which assets ship under an open license and which stay closed. Useful when the question is framed as one big yes or no. CX Codex +1 13,800installs windsurf-license-management Jeremy Longshore windsurf-license-management keeps track of Windsurf seats: builds a license inventory, sets who gets a seat, and turns usage into cost and audit reports. CX Codex +1 1installs

From the same set176

The whole set →
sales-engineer sales-engineer is a Codex subagent that maps customer requirements to product capabilities, surfaces integration prerequisites and tradeoffs, and supports pre-sales positioning. CX Codex ★ 6,505repo stars resume-refiner resume-refiner — a subagent for refining resumes, CVs, and LinkedIn profiles. Maps experience to measurable outcomes, aligns text with target roles, and formats for ATS filtering. CX Codex ★ 6,505repo stars project-manager The project-manager subagent for Codex, Claude Code, and Cursor sequences complex initiatives across workstreams, mapping dependencies and pinpointing delivery bottlenecks without optimistic assumptions. CX Codex ★ 6,505repo stars product-manager The product-manager subagent frames product choices around user impact, engineering constraints, and delivery risk. Use it to shape a feature or decide what should ship first. CX Codex ★ 6,505repo stars legal-advisor The legal-advisor subagent for Codex, Claude Code, and Cursor spots legal and compliance risks in product flows, UI copy, and data handling before counsel review. CX Codex ★ 6,505repo stars growth-loops Maps product growth loops, measures their steps, and suggests experiments for the weakest link. Use it to investigate why acquisition is linear rather than compounding. CX Codex ★ 6,505repo stars customer-success-manager customer-success-manager — a subagent for mapping support patterns and adoption risks based on engineering data. Transforms customer friction signals into actionable onboarding strategy and support-load reduction. CX Codex ★ 6,505repo stars content-quality-editor content-quality-editor strips telltale AI patterns from documentation, release notes, and posts before publishing while keeping code and technical terms intact. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open