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 skills add potpie-ai/potpie --skill potpie-infra-architecturegit 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-infra-architecture)<a href="https://agentmods.dev/skills/potpie-ai/potpie/potpie-infra-architecture"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-infra-architecture/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/potpie-ai/potpie/potpie-infra-architecture"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-infra-architecture.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.00043 | $0.00556 |
| Opus 5 | $0.00022 | $0.00278 |
| Sonnet 5 | $0.00009 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
potpie-infra-architecture 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Potpie Infra Architecture
Use this skill when the task touches environments, adapters, deployment behavior, runtime config, service dependencies, production incidents, or architecture changes.
Fast Path
Start from the service, environment, adapter, or dependency named by the task. Resolve identity before assuming keys:
potpie graph search-entities "<service env adapter dependency>" --limit 10
Read the service neighborhood with the graph workbench:
potpie graph read \
--subgraph infra_topology \
--view service_neighborhood \
--scope service:<service-name> \
--environment <dev|staging|prod|preview> \
--depth 2 \
--direction both \
--limit 20
Omit --environment only when the task is environment-agnostic. For broad
architecture work, run potpie --json graph describe infra_topology --view service_neighborhood --examples before choosing the read shape.
Apply Results
Use infra context for blast radius, where-to-look decisions, deployment changes, adapter selection, and incident debugging. Preserve environment qualifiers; a staging dependency is not proof of a production dependency.
Look for explicit topology facts: DEFINED_IN, DEPLOYED_TO, DEPENDS_ON,
USES, EXPOSES, HOSTED_ON, and OWNED_BY.
Record Architecture
Record only source-backed topology or carefully labeled agent inferences. Use
authoritative_fact when evidence is an explicit source of truth such as
deployment config, service manifest, infra doc, ADR, or user statement. Use
agent_claim for lower-authority interpretation.
Use the workbench write flow:
potpie --json graph catalog --task "record infra architecture"
potpie graph search-entities "<service>" --type Service --limit 10
potpie --json graph describe infra_topology --view service_neighborhood --examples
potpie --json graph propose --file mutation.json
potpie --json graph commit <plan_id> --verify
potpie --json graph history --plan <plan_id>
Every durable infra fact needs an environment when the fact differs by environment, evidence when available, and a retrieval-grade description.
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.
- 11d ago First seen · 71 lines · 43 tokens per session scan A 26c8abf56d91
potpie-infra-architecture is a skill published in the GitHub repository potpie-ai/potpie (5,717 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 556 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
oracle-mcp-server-helper
Wire the oracle-database-mcp-server into a Python project so an LLM agent can call listtables / describetable / runsql / vectorsearch at inference time. Handles install, stdio launch, and LangChain tool conversion via langchain-mcp-adapters. Use whenever a project needs a Grok 4 / GPT-class agent that talks to a live…
astra-vector-backend
Design Astra DB Data API and vector-search backends for retrieval, metadata filtering, and LangChain-compatible stores.
langchain_patterns
Implement Retrieval-Augmented Generation (RAG) systems with LangChain4j. Build document ingestion pipelines, embedding stores, vector search strategies, and knowledge-enhanced AI applications. Use when creating question-answering systems over document collections or AI assistants with external knowledge bases.
langchain_patterns
Implement Retrieval-Augmented Generation (RAG) systems with LangChain4j. Build document ingestion pipelines, embedding stores, vector search strategies, and knowledge-enhanced AI applications. Use when creating question-answering systems over document collections or AI assistants with external knowledge bases.
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
eve
Build durable backend AI agents with the eve framework. Use when creating, editing, or debugging an eve project — agent instructions, skills, tools, connections, channels, sandboxes, subagents, schedules, or evals.