@agentyx/cli
Provider-agnostic CLI for selecting Agentyx capability packs and installing their Skills/MCP configuration into local coding-agent targets.
pnpm dlx @agentyx/cli init --pack technical --pack typescript --target codex --yes
pnpm dlx @agentyx/cli doctor
pnpm dlx @agentyx/cli install --dry-run
pnpm dlx @agentyx/cli install
Configuration is pack-first:
{
"packs": ["technical", "typescript", "angular", "efficiency"],
"enable": ["rtk"],
"targets": ["codex", "kimi"]
}
packs always install their lightweight Skills. Optional heavier capabilities such as rtk or
codebase-memory are active only when listed in enable or passed with --enable for that run.
Use agentyx configure --exclude skill:api-design --yes to remove a declared capability from the
effective harness, or agentyx configure --include skill:api-design --yes to remove that exclusion.
--include does not activate optional capabilities; it returns them to normal pack semantics.
Useful inspection commands:
agentyx pack show efficiency
agentyx skill list
agentyx mcp list
agentyx target list
agentyx source show superpowers
agentyx source inspect superpowers
agentyx graph
agentyx report
agentyx graph --format mermaid
agentyx graph owner authentication
Project Graph records direct architectural relationships in .agentyx.json and exposes text,
JSON, Mermaid and SVG projections. It is not a package dependency graph. Repository/docs/MCP
references are descriptive: Agentyx does not fetch or index related repositories. Configured
project facts and optional internal context are installed as one provider-neutral
agentyx-project-context Skill through the normal adapter lifecycle.
Interactive init offers existing check, test, build, and lint scripts only when the
package manager is unambiguous. Suggestions start unselected, are stored as instruction data, and
are never run by Agentyx. Non-interactive init leaves context absent.
doctor --check keeps normal human or JSON output, but exits with code 1 on warnings as well as
errors so CI can fail before install drift turns into a broken run.
Project-owned packs can reference standard SKILL.md directories declared through
skillDirectories and localPacks in .agentyx.json. Paths are project-relative and Agentyx
rejects symlinks that resolve outside the project.
For exact CLI pinning, committed lockfiles, fresh-checkout verification, and lock recovery, see the reproducibility guide.
Trusted external sources can be declared through trustedSources and inspected locally. The initial
Superpowers integration validates the local .codex-plugin/plugin.json and Skill inventory, but
keeps installation disabled until Agentyx can preserve resource-bearing Skill directories.