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 commands/potpie-ai/potpie/potpie-featuregit clone --depth 1 https://github.com/potpie-ai/potpieWhat 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.00000 | $0.00215 |
| Opus 5 | $0.00000 | $0.00108 |
| Sonnet 5 | $0.00000 | $0.00043 |
| Haiku 4.5 | $0.00000 | $0.00021 |
Grade A, and why
potpie-feature 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
Use Potpie context before feature work. Load potpie-project-preferences first,
and load potpie-infra-architecture when the change touches services,
deployment, adapters, or runtime behavior.
If the potpie CLI is available, read the graph directly:
potpie --json graph catalog --task "feature work in repo:<owner/repo>"
potpie --json graph describe decisions --view preferences_for_scope --examples
potpie graph read --subgraph decisions --view preferences_for_scope --scope repo:<owner/repo>
potpie graph read --subgraph decisions --view active_decisions --scope repo:<owner/repo>
potpie graph read --subgraph infra_topology --view service_neighborhood --scope service:<name> --depth 2
Expand the user's request into a good retrieval --query/query (add symptoms and
synonyms a future searcher would type). Inspect coverage, freshness, quality,
fallbacks, open conflicts, and source refs before relying on the result.
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 · 18 lines · 0 tokens per session scan A 37376dd13143
potpie-feature is a command published in the GitHub repository potpie-ai/potpie (5,702 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 215 tokens. 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 commands, from other repositories
xp-builder
Run the real Limitless XP Builder backend instead of simulating the session.
xp-answer
Send the learner's next answer into the currently active XP session.
xp-debrief
Run the real Limitless XP Debrief backend instead of simulating scoring in chat.
xp-hint
Use the active XP session and request a hint from the real backend.
xp-finish
Finish the active XP session using the real backend.
xp-status
Show the active XP session status from the real backend.