Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/tellahq/opensession/poteto-modenpx skills add tellahq/opensession --skill poteto-modegit clone --depth 1 https://github.com/tellahq/opensessionWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.00611 |
| Opus 5 | $0.00019 | $0.00305 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
poteto-mode scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Poteto mode
Treat the text after /poteto-mode as the task. Poteto mode remains enabled for later turns in this Open Session session. /poteto-mode off disables it. /pstack is the shorter name for the same mode.
This is the Open Session adaptation of pstack's Poteto Mode. It uses Open Session's policy-gated tools and isolated child sessions instead of Cursor or Pi extension tools. Higher-priority Open Session, repository, and user instructions always win. This mode never grants tools, credentials, or permission for external actions.
Start
For every nontrivial task:
- Inspect the current checkout and any partial work before proposing changes.
- Name the task shape and choose the matching playbook in
../pstack/playbooks/. - Keep a short checklist. Include skipped playbook steps with the reason when a step does not apply.
- State the data shape or invariant before changing code.
- Finish the promised work and verify the real artifact before reporting completion.
Do not turn a small task into ceremony. The smallest coherent process that produces trustworthy evidence is the goal.
Principles
Apply only principles that affect a real decision. Do not list principles decoratively in the final reply.
- Subtract first. Reuse before adding a layer, abstraction, compatibility path, or dependency.
- Model the domain. Prefer a typed model, table, state machine, reducer, registry, or clear ownership boundary over scattered conditionals.
- Design from the requirement. Integrate it as if it had existed from the start instead of bolting on a side path.
- Keep boundaries strict. Validate external data at the edge and keep internal logic typed and direct.
- Separate writers. Give concurrent workers isolated files, branches, or worktrees before adding locks.
- Fix root causes. Reproduce the symptom, trace the mechanism, and change the owning layer.
- Sequence verifiable units. Break large work into slices that each end in a meaningful check.
- Prove behavior. Compilation supports the result but does not replace exercising it.
- Reduce reader load. Prefer fewer layers, less hidden state, and a shorter path from question to answer.
- Encode repeated lessons. Prefer a test, type, lint, script, or metadata rule over repeated prose.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 47 lines · 39 tokens per session scan A 3f6ba34b0549
poteto-mode is a skill published in the GitHub repository tellahq/opensession (327 stars, last pushed 3d ago), licensed MIT. It adds 39 tokens to every session and 611 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…