- 27
- plugins
- 19
- skills
- 4
- servers
A minimal contribution graph of the repository: twenty weeks of commits, day by day, read from git.
A pomodoro beside the agent: the time running in the bar, a sound and a notification when a session ends, and the last seven days in a drawer.
GSD (Get Shit Done) beside the agent: where the milestone stands in .planning/, the next step one click away, and a plan's checkpoint answered over the agent's pane.
Conformance portable hooks: the same guard as hook-plugin with nothing behind it, so an allowed call proves the intercepted tool really ran. hook-plugin keeps the second handler that must never be reached.
Conformance hook ask effect on the shell alias: the guard asks only for a command carrying
lab-deny.Conformance hook effects on the shell alias: a deny group whose guard denies only a command carrying
lab-deny, followed by a second handler that must not run after a denial and must run after an allow.Conformance hook events: an observing group per event (session start, after a shell call, at the end of a turn), each recording that it ran.
Conformance exec-form hook: a deny group whose guard is a JavaScript file named by its path, not executable, so its extension picks the launcher, and given a word no shell may read.
Conformance fixture: a deny hook whose handler cannot run (missing script) — exercises the fail-closed contract (ADR-033) against real harnesses.
Conformance unmet requirement: a deny group whose exec-form guard is a Python script, on a Lab image that carries no python3, so the requirement report must name it and the guard must fail closed.
Conformance portable hooks: a two-handler PreToolUse group whose first handler always denies — the second handler must never run. Mirrored under a native matcher for the OpenCode vertical's MCP tool.
Conformance portable hooks: one group whose first handler denies the shell tool when the call mentions
secrets, and whose second handler denies with its own marker — so the deny scenario proves first-deny-wins by that marker's absence. A parallel native-matcher group intercepts the conformance MCP tool for the OpenCode vertical, whose runtime exposes no shell tool.Conformance deny after a shell call: the guard denies a command carrying
lab-denyonce it ran, so the reason must reach the model in the harness's own dialect.Conformance deny on the file.read alias: a guard that denies only a path carrying
lab-deny, followed by a second handler that must not run after a denial. Reading is a tool some harnesses never ask permission for, so the denial has to hold without a prompt.Conformance hook rows: a census group with no matcher recording the name and input every tool reaches a hook with, and one observing group per portable tool alias, each matched on the alias alone, so a harness binding an alias to the wrong native tool or field leaves that row's record missing.
Conformance fixture: an observational SessionStart hook beside a PreToolUse one, proving the session-start event where a harness has it and its Unsupported report where it does not.
Conformance hook transform effect on the shell alias: the guard rewrites every
lab-side/fromin the call's input tolab-side/to.Conformance lifecycle: a Skill, an agent and a hook whose version the lifecycle contract moves from V1 to V2 and then removes, asserting each move from what the harness loads.
1 skillA ping-pong plugin declaring every capability UZE delivers, for trying a harness by hand.
3 skills · 1 serverA ping-pong plugin declaring every capability UZE delivers, for trying a harness by hand.
3 skills · 1 serverConformance explicit route: a package shipping Codex's own envelope, which declares its skills but no MCP servers, beside an Agent Plugins root manifest, which Codex reads first. Each capability must load once.
1 skill · 1 serverConformance plugin rules: one glob rule, which the rules contract declares in one project and leaves out of another on the same machine, asserting it fires only in the declaring one.
UZE's own agentic Skills: making a project's instructions context (AGENTS.md) portable, writing the rules that apply only where they are relevant, working in the checkout UZE placed you in, writing the diagrams it keeps under
6 skillsagents-mdarchitecturecontextworkspace.artifacts, authoring plugins of your own, and the extensions they carry, and trying the marketplace's example plugins — each one reasoning over a deterministicuzeCLI that is the only thing that ever mutates or judges anything.uze's own workspace extensions in one package: GSD beside the agent, a pomodoro, and the repository's contribution graph; each one off until you allow and enable it.
