Skip to content
Baseline

INSTALLATION

Static files. Explicit adoption.

Baseline installs as portable Agent Skills. It adds no consumer runtime, telemetry, daemon, package manager, or generated build output to your project.

Current releasev0.5.0

01 / CLIENT

Choose the route your agent supports.

These commands are a static snapshot of the current published release.

01

Codex

Pinned release

codex plugin marketplace add woliveiras/baseline --ref v0.5.0
codex plugin add baseline@baseline

The marketplace is pinned to the immutable v0.5.0 release. Start a new Codex session after installation.

02

GitHub Copilot

Marketplace

copilot plugin marketplace add woliveiras/baseline
copilot plugin install baseline@baseline

Copilot follows the repository marketplace. Its current command does not expose Codex's explicit tag pin.

03

Claude Code

Mutable channel

claude plugin marketplace add https://github.com/woliveiras/baseline.git
claude plugin install baseline@baseline

This short HTTPS route follows the default branch. Use the tag-qualified route in the full guide when reproducibility matters.

STANDALONE AGENT SKILLS

Cursor and OpenCode

Install the published tag into $HOME/.baseline and link its canonical skills into $HOME/.agents/skills. The full block refuses to overwrite an existing skill.

Open the standalone guide

LOCAL PACKAGE

Pi

Use the pinned repository checkout and its dependency-free Pi descriptor. The guide includes installation, listing, reinstall, and removal.

Open the Pi guide

02 / PROJECT

Initialize the engineering contract.

Client installation makes the skills discoverable. It does not modify the repository. Start a new agent session at the project root and invoke setup once.

Use $setup-baseline to create or safely reconcile this project's AGENTS.md.
  • Inspects current project evidence before writing.
  • Preserves stronger existing instructions.
  • Stops for material conflicts instead of overwriting them.
  • Does not install a runtime or commit the resulting file.

EVIDENCE LIMIT

Discovery is not behavioral certification.

An installation check can establish that a client sees the skills. It does not prove that a particular model, version, configuration, or session will select and follow every workflow correctly. Keep client evidence named and bounded.

See how claims are bounded