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-source-ingestiongit 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-source-ingestion)<a href="https://agentmods.dev/skills/potpie-ai/potpie/potpie-source-ingestion"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-source-ingestion/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-source-ingestion"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-source-ingestion.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.00082 | $0.03368 |
| Opus 5.5 | $0.00033 | $0.01347 |
| Sonnet 5.5 | $0.00016 | $0.00674 |
| Haiku 4.5 | $0.00008 | $0.00337 |
Grade A, and why
potpie-source-ingestion 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Potpie Source Ingestion
Use this skill for explicit ingestion requests. The harness is the intelligence: it gathers source data, reads it, decides what is durable, resolves identity, and writes semantic graph mutations with evidence. Potpie validates and stores; it does not decide what source material means.
Non-Negotiables
- Use a todo/checklist for every repository or multi-source ingestion. Do not jump directly from a README to graph writes.
- Local inspection is required for repo understanding. Scanner-driven graph
updates are forbidden. Inspect files with
rg,rg --files,git, and structured tooling; do not run legacy or deterministic ingestion/scanner commands that walk the tree and write graph facts. - Use subagents only for read-only discovery slices. The main agent owns source selection, identity resolution, mutation proposals, commits, and final synthesis.
- Do not write until each required discovery lane is complete, explicitly unavailable, or intentionally scoped out by the user.
- Every write needs source refs, source authority, truth class, confidence, compact summary, and retrieval-grade description.
Phase 0: Scope And Preflight
- Define source kind, pot/project, repo/path/URL, time window, and target memory shape: baseline, history, docs, infra, debug memory, preferences, or all.
- Verify Potpie scope and graph availability with one call:
potpie status
It reports the daemon, the active pot, backend readiness and claim counts;
every later read names the pot it used in its header, so do not pre-read
pot info, source list or graph status. Pass --pot <name-or-id> on later
calls once the pot is known.
- If the repo is not registered, register metadata only. Use explicit
--potwhen pot scope is ambiguous:
potpie source add repo . --pot <pot-id-or-name>
- Inspect the full destination ontology before selecting mutation shapes:
potpie --json graph catalog --profile full --pot <pot>
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 Changed · +53 lines 29bf24a42326
- 1mo ago First seen · 249 lines · 82 tokens per session scan A acf24c5e5449
potpie-source-ingestion is a skill published in the GitHub repository potpie-ai/potpie (5,743 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 3,368 once invoked, about $0.0003 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
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.
llamaindex
Data framework for building LLM applications with RAG. Specializes in document ingestion (300+ connectors), indexing, and querying. Features vector indices, query engines, agents, and multi-modal support. Use for document Q&A, chatbots, knowledge retrieval, or building RAG pipelines. Best for data-centric LLM…
gog-workspace
Use the gog CLI for Google Workspace tasks across Gmail, Calendar, Drive, Docs, Sheets, Contacts, and related services. Use when the user asks to check email, search Gmail, inspect calendar events, find Drive files, read Docs or Sheets, or manage Google Workspace data through gog.
ima-skill
A unified IMA skill for managing personal notes and knowledge bases through the platform's APIs.
notes
A note-management skill for searching, reading, creating, and adding content to personal notes in IMA, a note and knowledge platform.