potpie-project-preferences

A project-preferences lookup for coding work. It finds the repository's existing choices for errors, tests, folders, dependencies, security, APIs, naming, and other coding practices.

In plain words
What is it for?
Use it before writing, changing, reviewing, refactoring, or testing code, and afterward when a new reusable project preference should be recorded.
Why use it?
It prevents an agent from guessing how a project should be changed or repeatedly rediscovering the same rules. The found preferences are treated as constraints during the work.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/potpie-ai/potpie/potpie-project-preferences
Any agent
npx skills add potpie-ai/potpie --skill potpie-project-preferences
Clone the repo
git clone --depth 1 https://github.com/potpie-ai/potpie

Made for: Claude Code, Codex.

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 551 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00063 $0.00551
Opus 5 $0.00032 $0.00275
Sonnet 5 $0.00013 $0.00110
Haiku 4.5 $0.00006 $0.00055

Measured yesterday against content hash a7aee2c8feda, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

potpie-project-preferences 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.

potpie/cli/templates/agent_bundle/.agents/skills/potpie-project-preferences/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Potpie Project Preferences

Use this skill before implementation or review so local conventions shape the work instead of being rediscovered from code.

Fast Path

  1. Identify the narrowest scope you know: repo, path, service, package, or file.
  2. Expand the user's task into preference search terms: error handling, retries, validation, logging, observability, framework, folder layout, tests, dependency choice, security, API shape, naming.
  3. Read preferences with the graph workbench:
potpie graph read \
  --subgraph decisions \
  --view preferences_for_scope \
  --scope repo:<owner-repo>,path:<path-or-dir> \
  --query "<expanded preference query>" \
  --limit 12

If the scope is unclear, first use potpie --json pot info and potpie --json source list, or search entities:

potpie graph search-entities "<repo service package>" --type Service --limit 10

Apply Results

Treat returned preferences as implementation constraints. Prefer active, higher-confidence, closer-scope preferences over broad ones: file, directory, service, repo, global. If two preferences conflict, verify source refs or ask the user before choosing.

Do not quote Potpie context back unless it matters. Use it to write better code.

Record A Preference

Record only reusable, explicit preferences that are likely to matter again. Do not turn one-off implementation choices into project policy.

Use the workbench write flow:

potpie --json graph catalog --task "record coding preference"
potpie graph search-entities "<scope>" --type Service --limit 10
potpie --json graph describe decisions --view preferences_for_scope --examples
potpie --json graph propose --file mutation.json
potpie --json graph commit <plan_id> --verify
potpie --json graph history --plan <plan_id>

A good preference write includes the policy kind, prescription, strength, audience, scope, truth class, evidence or source refs when available, and a retrieval-grade description with the terms future agents would search.

Read the full file on GitHub · 67 lines

Changes

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.

  1. yesterday First seen · 67 lines · 63 tokens per session scan A a7aee2c8feda

Subscribe to this mod's changes

potpie-project-preferences is a skill published in the GitHub repository potpie-ai/potpie (5,702 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 551 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

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…

oracle-devrel/oracle-ai-developer-hub · 110 tokens

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…

oracle-devrel/oracle-ai-developer-hub · 72 tokens

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.

oracle-devrel/oracle-ai-developer-hub · 40 tokens

skill-creator

Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.

oracle-devrel/oracle-ai-developer-hub · 28 tokens

build-paths-intermediate

Scaffold a Grok-4 tool-calling agent over an Oracle schema using langchain-oracledb + oracle-database-mcp-server + in-DB ONNX embeddings (registered MiniLM model, no external embedding API) + Open WebUI. For users who've built RAG before and want to rebuild it on the production-feeling Oracle stack.

oracle-devrel/oracle-ai-developer-hub · 78 tokens

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…

oracle-devrel/oracle-ai-developer-hub · 0 tokens