patina-mode
Patina mode
Platform Adaptation
These skills use Claude Code tool names (the Skill tool, the Agent tool, AskUserQuestion) and Claude model slugs (claude-*). On Claude Code they work as written. On Codex, read references/codex-tools.md for the Codex equivalent of a Claude tool, model, or built-in skill (run, verify, plugin-dev:skill-development). On Pi, read references/pi-tools.md instead. Other runtimes can discover the same Agent Skills tree, but they must use their own tool, model, and configuration equivalents. Neither mapping is a cross-runtime map.
On Codex, patina-mode requires the multi_agent feature. Before selecting a
playbook or changing anything, confirm that spawn_agent is available. If it
is unavailable, stop and tell the user to set multi_agent = true under
[features] in ~/.codex/config.toml, then restart Codex. Do not continue with
a sequential substitute.
Non-negotiables
The Principles section below grounds every trigger. Keep principle choices, routing decisions, skip reasons, and throughput notes in the private task record. Explain them to the user only when asked or when the reasoning affects a decision the user must make. Cite only principles whose leaf SKILL.md you read this session.
While patina-mode is active, this skill owns workflow routing. Use only the skills and playbooks named here. Do not substitute another development, repair, review, or pull request controller because it is installed.