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-change-timelinegit 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-change-timeline)<a href="https://agentmods.dev/skills/potpie-ai/potpie/potpie-change-timeline"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-change-timeline/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-change-timeline"><img src="https://agentmods.dev/badge/skills/potpie-ai/potpie/potpie-change-timeline.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.00550 |
| Opus 5 | $0.00022 | $0.00275 |
| Sonnet 5 | $0.00009 | $0.00110 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
potpie-change-timeline 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 10d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Potpie Change Timeline
Use this skill when the user asks what changed, when debugging a possible regression, or when ingesting source history from GitHub, Linear, Jira, docs, or deployment records.
Fast Path
Read the project timeline first. A pot is the project boundary and can contain multiple repos, so do not narrow to the current repo unless the user asks.
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--time-window 7d \
--limit 20
Use the user's exact dates when provided:
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--since 2026-06-01 \
--until 2026-06-15 \
--limit 50
Only narrow when the user gives a service, environment, or topic:
potpie graph read \
--subgraph recent_changes \
--view timeline \
--format table \
--scope service:<service-name> \
--query "<symptom feature deployment>" \
--time-window 14d \
--limit 20
Apply Results
Timeline context is correlation, not proof. Use it to choose files, PRs, tickets, or deploys to inspect, then verify the source ref before blaming a change. Timeline reads do not include uncommitted local work unless it was recorded.
Record History
For GitHub, Linear, Jira, docs, and similar sources, hydrate records with the agent's integration tools/connectors first. Do not use Potpie CLI queue ingestion as the source-history path.
Use the workbench write flow after reading the source:
potpie --json graph catalog --task "record timeline change"
potpie --json graph describe recent_changes --view timeline --examples
potpie --json graph propose --file mutation.json
potpie --json graph commit <plan_id> --verify
potpie --json graph history --plan <plan_id>
Use the source event time for occurred_at, not ingestion time. Add fixes,
decisions, bug patterns, or infra links only when the source explicitly supports
them.
Timeline capture is harness-led. Do not use scanner-driven graph updates or turn source titles into facts without reading the source.
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.
- 10d ago First seen · 79 lines · 43 tokens per session scan A 298f5ac59041
potpie-change-timeline is a skill published in the GitHub repository potpie-ai/potpie (5,715 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 550 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
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.
soccer-workshop-setup
Bootstrap the soccer analytics agent workshop. Starts the Oracle AI Database Free container, applies schema, loads the FIFA dataset, optionally trains models, populates LangChain OracleVS hybrid retrieval plus semantic memory, applies LangGraph OracleDB observability, and verifies OCI GenAI access. Use when starting…
design-taste-frontend
Senior UI/UX Engineer. Architect digital interfaces overriding default LLM biases. Enforces metric-based rules, strict component architecture, CSS hardware acceleration, and balanced design engineering.
skill-creator
Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
build-paths-advanced
Scaffold an agent system where Oracle AI DB is the only state store, composed from the build-paths/skills/ building-block library. Stack — langchain-oracledb + oracle-database-mcp-server + in-DB ONNX embeddings + OCI GenAI Grok 4 + Open WebUI. Three projects — production-feeling NL2SQL+RAG hybrid analyst…