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 acolomba/pi-claude-marketplace --skill claude-code-compat-researchgit clone --depth 1 https://github.com/acolomba/pi-claude-marketplaceWrote 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/acolomba/pi-claude-marketplace/claude-code-compat-research)<a href="https://agentmods.dev/skills/acolomba/pi-claude-marketplace/claude-code-compat-research"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/claude-code-compat-research/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/acolomba/pi-claude-marketplace/claude-code-compat-research"><img src="https://agentmods.dev/badge/skills/acolomba/pi-claude-marketplace/claude-code-compat-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00037 | $0.01729 |
| Opus 5.5 | $0.00015 | $0.00692 |
| Sonnet 5.5 | $0.00007 | $0.00346 |
| Haiku 4.5 | $0.00004 | $0.00173 |
Grade A, and why
claude-code-compat-research 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 23d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code compatibility research
pi-claude-marketplace gives Pi users the Claude plugin ecosystem: it installs real plugins from real Claude marketplaces and translates their components into Pi-native artifacts. Every behavior it gets wrong is a behavior a user already learned in Claude Code and now has to unlearn. Upstream parity is the product, not a courtesy.
So the default is to match Claude Code. Exactly two things license a divergence:
- A recorded project decision. AGENTS.md carries these with IDs -- SC-1, for instance, declines Claude Code's
localscope and keeps exactlyuserandproject. - A capability gap in Pi. Pi has no equivalent for the upstream behavior, so parity is not available at any price.
"Upstream looks wrong to me" and "our way is simpler" are not licenses. A divergence that fits neither category is a question for the user, not a decision to settle inside the discussion.
Establish Claude Code's behavior before analyze_phase generates gray areas.
First decide whether the phase touches the upstream contract
Not every phase does. Internal error plumbing, test structure, and Pi-only surfaces have no upstream analogue, and inventing one wastes the discussion.
Answer this in one line before researching anything. Research the phase if it touches component translation, install lifecycle, the command surface, scope, or enablement state -- anything a Claude Code user would recognize. Otherwise record that no upstream position applies and recommend from Pi and project constraints.
Component reference
pi-claude-marketplace bridges six component kinds. Parity is the goal for each:
The container and lifecycle surface around them:
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.
- 23d ago Changed 6ad36eea16a9
- 1mo ago Changed · +1 lines 883042a3889e
- 1mo ago First seen · 92 lines · 37 tokens per session scan A 071a4bff69b8
claude-code-compat-research is a skill published in the GitHub repository acolomba/pi-claude-marketplace (28 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 1,729 once invoked, about $0.0001 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-09-23.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…