Menu

Individual skill

poteto-mode

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Invoke explicitly with $poteto-mode.

skills/poteto-mode/SKILL.md

Read pinned source

Source commit d5b20bce6f0602e3155960b5ea46e47fa0692ad2

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Network or broad shell
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
105
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Poteto mode

All delegation, lifecycle, isolation, history, connector, and capability behavior follows `references/codex-agent-runtime.md`. A playbook may narrow that contract but never broaden it.

## Codex session lifecycle

An explicit invocation must appear first after whitespace in the user prompt. Accept `$poteto-mode`, `$pstack-for-codex:poteto-mode`, or a Codex Markdown skill link with either exact label. The link must target a normalized absolute local path ending in `/skills/poteto-mode/SKILL.md`. This explicit invocation applies the complete skill on the activation turn. A trusted bundled hook records only session-scoped activation metadata for later turns. Casual mentions, quoted examples, and the words “poteto mode” do not activate it.

The exact phrase `disable $poteto-mode` opts the current session out. It removes only that session's state. Session end is advisory because Codex can resume the same session. State expires through the bundled versioned TTL collector instead.

The activation hook adds a `Poteto sticky receipt` context line when it ran successfully. If that receipt is absent, unknown, stale, or reports a mismatch, follow this skill for the current turn and state that cross-turn sticky behavior is inactive because trusted hooks could not be verified. Never infer global or cross-session activation.

Later active turns receive compact developer context from the hook. Compaction and resume use the same stable session state and must not duplicate the mode wrapper. Only the exact `pstack-poteto-agent` custom profile receives hook-provided subagent context. When that profile is unavailable, include `references/poteto-agent-prompt.md` in the generic delegate's task prompt. Generic delegates never inherit Poteto Mode merely because the parent session is active.