Potpie is a tool that turns a software repository and its development history into a context graph for AI coding agents. Agents use that graph to answer codebase questions, plan changes, debug problems, and write code with project-specific information. The catalogue includes skills, hooks, commands, and a plugin for integrating Potpie into coding-agent workflows.
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/potpie-ai/potpie/potpie-debug-memorynpx skills add potpie-ai/potpie --skill potpie-debug-memorygit clone --depth 1 https://github.com/potpie-ai/potpieWrote 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/potpie-ai/potpie/potpie-debug-memory)<a href="https://agentmods.dev/skills/potpie-ai/potpie/potpie-debug-memory"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-debug-memory.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00041 | $0.00573 |
| Opus 5 | $0.00020 | $0.00287 |
| Sonnet 5 | $0.00008 | $0.00115 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
potpie-debug-memory 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Potpie Debug Memory
Use this skill before digging into a failure so prior symptoms, known fixes, and failed attempts can guide the investigation.
Fast Path
Search by symptom first, not just component name. Include exact error text, commands, failing tests, environment, service, dependency, and synonyms.
potpie graph read \
--subgraph debugging \
--view prior_occurrences \
--query "<expanded symptom query>" \
--scope service:<service-name> \
--limit 12
If no service is known, omit --scope. If the failure smells like a regression,
correlate with the timeline:
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--time-window 7d \
--query "<symptom feature dependency>" \
--limit 20
If dependencies, adapters, environments, or deploys matter, read infra too:
potpie graph read \
--subgraph infra_topology \
--view service_neighborhood \
--scope service:<service-name> \
--depth 2 \
--direction both
Apply Results
Treat prior fixes as leads. Check whether the same symptom, environment, version, dependency, data shape, command, or test path matches this incident. Failed prior attempts are useful because they prevent repeated work.
Record Debug Memory
Record after the investigation when the learning is reusable: bug pattern, fix, verification, failed attempt, incident summary, runbook note, or setup gotcha.
Use the workbench write flow:
potpie --json graph catalog --task "record bug fix"
potpie graph search-entities "<service or symptom>" --limit 10
potpie --json graph describe debugging --view prior_occurrences --examples
potpie --json graph propose --file mutation.json
potpie --json graph commit <plan_id> --verify
potpie --json graph history --plan <plan_id>
Good debug memory includes the distinctive error text, repro signal, root cause or uncertainty, fix steps, verification status, scope, truth class, evidence, and a retrieval-grade description with symptom synonyms.
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.
- 5d ago First seen · 80 lines · 41 tokens per session scan A f3fdab1915bd
potpie-debug-memory is a skill published in the GitHub repository potpie-ai/potpie (5,710 stars, last pushed yesterday), licensed Apache-2.0. It adds 41 tokens to every session and 573 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
mem-setup
This skill should be used when the user asks to "set up claude-mem", "pair claude-mem", "connect cmem", "add my cmem key", "set up cloud sync in Cowork", or provides cmem.ai Connect values (sync token, user id, SyncHub URL) for this plugin. Configures the claude-mem-cowork plugin credentials.
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
aatmf-t04-memory-manipulation
AATMF T4 — Multi-Turn & Memory Manipulation. Persistent memory injection, conversation-state poisoning, cross-session contamination, ghost-context leak.
openmemory
Manage persistent memory via OpenMemory MCP. TRIGGER when: user says "remember this", "save to memory", "store this", "recall", "what do you remember about", "check memory", "forget this", "delete memory", "clean up memory", or when agent forms a stable conclusion worth persisting. DO NOT TRIGGER when: user refers to…
hivemind-memory
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.