One profile · seventeen harnesses

Apothem

One profile, every harness.

Write your rules, skills, hooks, and commands once in a single shared profile — Apothem renders them into the native configuration of seventeen harnesses, each in the exact format that tool reads.

Latest published version (opens in new tab)

Install Apothem Quickstart

install

# Claude Code plugin (inside Claude Code)$ /plugin marketplace add ahmed-g-gad/apothem

# npx — any machine with Node and Python 3.10+$ npx @ahmed-g-gad/apothem quickstart

# one-shot installer (POSIX)$ curl -fsSL https://apothem.ahmedgad.com/install.sh | bash

Renders native config for

Claude Code
Cursor
Gemini CLI
GitHub Copilot
Codex
Windsurf
Zed
OpenCode
Qwen Code
Kiro
Trae
CodeBuddy
Antigravity
Hermes
Open-Claw
Kimi Code
GLM (Z.ai)

One source of truth, kept honest

The synced unit is wider than rules alone, and the discipline to keep it correct ships in the box.

One profile, seventeen harnesses

A single shared profile at ~/.config/apothem/profile.yaml renders into the native config of seventeen harnesses — each adapter writes the format that tool actually reads.

A governed synced unit

Rules, skills, hooks, slash-commands, and MCP servers travel together as one governed source — not rules alone, and not arbitrary files.

A conformity gate that ships with it

Behavioral rules plus a mechanical conformity gate (python -m apothem.conformity.gate) come bundled, so the profile itself is held to a fifteen-bar pre-emission standard.

Deterministic plan & research pipelines

A deterministic /plan-spec to /plan-execute pipeline and a thirteen-stage /research pipeline run inside the tool — every option set carries a recommended choice, never a silent default.

An eleven-command audit fortress

Code, security, performance, accessibility, dependency, supply-chain, and threat-model audits sweep in one parallel pass, then /fortress remediates and re-audits in a bounded loop.

Durable memory, opt-in learning

A two-tier memory carries conventions across sessions; the learning loop is default-off under the agnostic posture — a clean install never auto-applies a workflow.

Supply-chain hardened releases

Each tagged release attaches signed artifacts — sdist, wheel, SBOM, Sigstore cosign signature, SLSA provenance, and npm provenance — with an OpenSSF Scorecard target on the producer pipeline.

Preview before any write

apothem diff --harness <name> shows every pending change to a tool config before it lands — inspect the full diff, then install.

Reversible, verified lifecycle

Every install backs up what it replaces; apothem verify --json reports drift; uninstall reverses cleanly with zero orphans left behind.

How Apothem compares

The category is contested, not empty. Here is where Apothem sits against the tools operators reach for first.

Capability	Apothem	File config managers	Cross-tool rule sync
One source to many tools' native schemas	seventeen harness adapters	copy or symlink, no translation	reaches more tools
Synced unit	rules, skills, hooks, commands, MCP		rules, MCP, commands, skills, hooks
Governance corpus with a mechanical conformity gate	python -m apothem.conformity.gate	config only	config only
Deterministic plan and research pipelines	/plan-spec to /plan-execute, thirteen-stage /research	none	none
Audit fortress that detects and remediates	eleven-command sweep, /fortress re-audit loop	none	none
Supply-chain hardened releases	SBOM, Sigstore, SLSA, npm provenance, Scorecard target	none	varies
Reversible, verified lifecycle	backup, verify --json drift, zero-orphan uninstall	varies	varies

Where a peer is stronger, it is named: cross-tool rule sync reaches more tools and carries a comparably wide synced unit, and several sync tools materialize native schemas. Apothem trades raw tool count for the governance, audit, and lifecycle discipline shipped around the sync — a conformity gate, deterministic pipelines, an audit fortress, and a reversible verified lifecycle.

See the full comparison

Configure once. Carry it everywhere.

Install in one command and preview every file each tool will write before anything lands.

Run the quickstart Compare alternatives