---
title: "veto-codex"
description: "How Veto works in Codex: research, design, implementation, verification and durable handoffs."
canonical: https://agentpluginsdirectory.com/plugins/veto-codex
last-updated: 2026-09-13
---

# veto-codex
How Veto works in Codex: research, design, implementation, verification and durable handoffs.
- Slug: veto-codex
- Publisher: Veto
- Repository: https://github.com/TryVeto/veto-codex
- Manifest: plugins/veto-codex/plugin.json
- Version: 2026.9.1203
- Category (editorial): other
- Skills: 13 (build-a-capability, field-proof, independent-judgment, integration-design, make-a-goal, product-design, product-sense, product-tests, remove-slop, review-a-prototype, sandbox-experience, veto-codex, work-control)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-09-13
- Repository last pushed: 2026-09-13
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/veto-codex
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What veto-codex does, in the publisher's words

Give the outcome. The agent carries the method.

Version 2026.9.1203 · 12 September 2026 · Renamed repository edition, continuing 2026.9.1202. New veto-codex identifier, 13 public skills and nine retained role guides. No second controller, new service, automatic hook, remote dependency or product deployment.

The existing veto-codex skill is the entry point. It selects the relevant procedure and keeps execution moving to the accepted result. Five contextual playbooks connect start/resume, investigation/build, manager return, finish/handoff and improvement of the method. Agents load them when needed, not as another giant prompt. Existing product, design, craft, review and integration skills remain in place.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/TryVeto/veto-codex/HEAD/plugins/veto-codex/README.md

## Skills

- build-a-capability: Implement or repair a Veto capability, local setup or CI; handle Git source handoffs and authorized preview delivery. Not read-only audits, planning, production operations or payment execution.
- field-proof: Design or analyze a permissioned Veto user study or benefit comparison. Use for comprehension, burden, adoption and repeat-choice evidence; not synthetic customer validation.
- independent-judgment: Form and defend an evidence-based recommendation on a consequential product or engineering choice, including disagreement with the founder. Not for manufacturing objections to routine work.
- integration-design: Select, specify or qualify a Veto integration or WorkOS environment/authentication boundary. Use for a consequential external route or auth configuration review; not routine inbox work or a connector catalog.
- make-a-goal: Write, adopt or revise a Veto goal below 4,000 characters. Separate the accepted vision from a bounded active bet; use native action and readback for adoption, and preserve scope and pause.
- product-design: Design Veto interactions, shared UI contracts/tokens, authorized structural changes or approved reference implementations. Use remove-slop for a bounded craft pass on an existing surface.
- product-sense: Choose Veto product priorities, first features, surfaces, or scope. Use for an unsettled product decision; not a routine approved implementation or cosmetic edit.
- product-tests: Define, run or assess Veto acceptance, Git candidate identity and WorkOS auth evidence; plan scoped production verification. Does not grant repair, release, access or customer-contact permission.
- remove-slop: Critique or refine an existing Veto interface: remove decorative eyebrows, repetition, fake reassurance and broken interaction. Preserve approved structure; critique stays read-only.
- review-a-prototype: Package or independently review a working prototype at an exact candidate. Use for Pro feedback or team-owned walkthroughs; not as a production release or customer-validation claim.
- sandbox-experience: Make Veto sandbox tasks self-serve: safe sample inputs, scenario controls, coherent state, reset and recovery. Use for demos or rehearsals, not production operations or OS isolation.
- veto-codex: Carry an authorized Veto outcome from context through working evidence and handoff. Select the needed procedure, coordinate contained help, and resume prior work without founder coaching.
- work-control

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.