Borrowing it
Nothing to install: this file belongs to tellahq/opensession. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tellahq/opensession/main/.agents/skills/pstack/SKILL.mdgit clone --depth 1 https://github.com/tellahq/opensessionWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/tellahq/opensession/pstack)<a href="https://agentmods.dev/skills/tellahq/opensession/pstack"><img src="https://agentmods.dev/badge/skills/tellahq/opensession/pstack/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tellahq/opensession/pstack"><img src="https://agentmods.dev/badge/skills/tellahq/opensession/pstack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00041 | $0.02027 |
| Opus 5.5 | $0.00016 | $0.00811 |
| Sonnet 5.5 | $0.00008 | $0.00405 |
| Haiku 4.5 | $0.00004 | $0.00203 |
Grade A, and why
pstack 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 1mo 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pstack mode
Treat the text after /pstack as the task. Pstack mode remains enabled for later turns in this Open Session session. /pstack off disables it. /poteto-mode is the longer name for the same mode.
This is the Open Session port of pstack's Poteto Mode. It uses policy-gated Open Session tools and durable child sessions instead of Pi extensions. Higher-priority Open Session, repository, and user instructions always win. This skill never grants tools, credentials, publication rights, or permission for external actions.
Start
For every nontrivial task:
- Inspect the current checkout and partial work before proposing changes.
- Read the matching playbook below. Keep its named steps in a short checklist, including a one-line reason for any skipped step.
- State the authoritative data shape or invariant before changing code.
- Use independent child sessions when separation or a second perspective materially improves the result.
- Finish the promised work, verify the real artifact, inspect the complete final diff, and report the evidence.
Do not turn small work into ceremony. Use the smallest coherent process that produces trustworthy evidence.
Required routing
- Architecture, ownership, or "are we sure?" questions use how.
- A fork that an experiment can settle uses the Prototype playbook. Ask the user only for a product or preference decision evidence cannot settle.
- Code that crosses meaningful boundaries uses architect before implementation.
- Coverage matrices and independent investigation slices use swarm. Competing implementations use arena.
- Contested designs and high-risk diffs use interrogate.
- Prose uses unslop. Documentation and PR prose also use technical-writing.
- Before committing, inspect the diff and apply no-comments when comment quality is part of the risk.
- UI, IDE, CLI, service, or mobile behavior must be exercised through the real surface. Reproduce bugs on the same surface first.
- PR monitoring uses Babysit. Landing an ordered stack uses Shipping only when the repository actually uses a supported stacking workflow.
- Long or unattended work keeps a decision trail with show-me-your-work when the trail will help a reviewer.
- A broken skill is fixed as its own scoped change. Do not silently route around it.
What ships with it
32 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.
- agents/comment-sicko.md 842 B
- agents/poteto-agent.md 471 B
- LICENSE 1.0 KB
- playbooks/authoring-a-skill.md 938 B
- playbooks/autonomous-run.md 1.2 KB
- playbooks/autopilot-full.md 1.4 KB
- playbooks/autopilot-stack.md 1.4 KB
- playbooks/babysit.md 1.5 KB
- playbooks/bug-fix.md 2.6 KB
- playbooks/eval.md 1.4 KB
- playbooks/feature.md 2.9 KB
- playbooks/hillclimb.md 4.4 KB
- playbooks/investigation.md 1.1 KB
- playbooks/multi-phase-plan.md 89 B
- playbooks/opening-a-pr.md 1.5 KB
- playbooks/orchestrate.md 2.0 KB
- playbooks/pause-safely.md 1.1 KB
- playbooks/perf-issue.md 3.5 KB
- playbooks/performance.md 1.0 KB
- playbooks/prototype.md 2.5 KB
- playbooks/refactor.md 1.1 KB
- playbooks/refactoring.md 3.9 KB
- playbooks/review.md 910 B
- playbooks/runtime-forensics.md 1.4 KB
- playbooks/session-pickup.md 1.1 KB
- playbooks/shipping.md 1.5 KB
- playbooks/trace-forensics.md 2.0 KB
- playbooks/visual-parity.md 1.3 KB
- playbooks/worktree-cleanup.md 1.4 KB
- references/bugbot-triage.md 9.4 KB
- references/plan.md 4.9 KB
- SOURCE.md 1.6 KB
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.
- 1mo ago Changed · +59 lines · +4 tokens per session 412e3d02c0fe
- 1mo ago First seen · 78 lines · 37 tokens per session scan A 032357c67e1f
pstack is a skill published in the GitHub repository tellahq/opensession (399 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 2,027 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…