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 agents/painhardcore/pstack/poteto-agentgit clone --depth 1 https://github.com/painhardcore/pstackWhat 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.00041 | $0.00113 |
| Opus 5 | $0.00020 | $0.00056 |
| Sonnet 5 | $0.00008 | $0.00023 |
| Haiku 4.5 | $0.00004 | $0.00011 |
Grade A, and why
poteto-agent 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 yesterday.
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.
What it actually says
Poteto subagent
You are operating as poteto-mode's full agent style. Read the poteto-mode skill's SKILL.md in full before doing any work, including its inline Principles index. Navigate to a leaf principle-* skill whenever you apply that principle.
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.
- yesterday First seen · 10 lines · 41 tokens per session scan A 796c13e4b703
poteto-agent is an agent published in the GitHub repository painhardcore/pstack (1 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 113 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-31.
Other agents, from other repositories
codealive-context-explorer
Iterative code exploration across indexed repositories using CodeAlive semantic search, grep, artifact fetch, and relationship inspection. Use proactively when investigating a codebase question, tracing cross-service patterns, understanding architecture, debugging, or gathering context from external repos. Almost…
antislop
Writing specialist that suppresses AI writing patterns. Two modes: (1) style mode, apply when writing, editing, or polishing any prose; (2) audit mode, score text 0-100 and list every violation when asked to check, grade, or flag AI patterns. Read-only, returns text or audit results for the primary agent to act on.
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
issue-tracker
Specs and tickets for this repository live as Markdown files under .scratch/.
triage-labels
These are the labels actually configured on this repo's Forgejo instance, with their descriptions as recorded there. Use these, not the default Matt Pocock triage set: needs-triage, needs-info, ready-for-human, and wontfix are not configured here.
domain
Read CONTEXT.md before changing rules, scoring, generated artifacts, or evaluation fixtures. Use its canonical terms in specs, tickets, tests, and documentation.