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 Poppify/poppify-claude-plugin --skill poppify-schema-introspectgit clone --depth 1 https://github.com/Poppify/poppify-claude-pluginWrote 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/poppify/poppify-claude-plugin/poppify-schema-introspect)<a href="https://agentmods.dev/skills/poppify/poppify-claude-plugin/poppify-schema-introspect"><img src="https://agentmods.dev/badge/skills/poppify/poppify-claude-plugin/poppify-schema-introspect/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/poppify/poppify-claude-plugin/poppify-schema-introspect"><img src="https://agentmods.dev/badge/skills/poppify/poppify-claude-plugin/poppify-schema-introspect.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.00094 | $0.01252 |
| Opus 5 | $0.00047 | $0.00626 |
| Sonnet 5 | $0.00019 | $0.00250 |
| Haiku 4.5 | $0.00009 | $0.00125 |
Grade A, and why
poppify-schema-introspect scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s https://poppify.ai/api/mcp \ How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inspecting the deployed Poppify MCP schemas
MCP clients strip undeclared fields before forwarding to the server. If a parameter you pass to a tool seems to have been ignored, the most likely cause is schema/code drift — the server's handler accepts the field, but the MCP tool registration's Zod schema doesn't declare it, so the field was dropped at the protocol boundary.
This skill teaches Claude how to verify the deployed schema directly.
Jul 2026 consolidation note: the deployed surface was consolidated from 37 tools to 28 — old names were merged, not dropped, and two NEW tools were added:
publish_post(post now / schedule to connected channels, linked accounts only) andportfolio(list / switch the active portfolio).customize/set_audio/set_voiceover→apply_session_patch;update_visual→update_slides({action:"set_image"})(replace) +apply_session_patch({visualEdits:[...]})(insert/splice);preview_live_prompt→animate_slide({dryRun:true});generate_frames→add_slide_image(reference params, consistent-frames mode);list_recipes/get_recipe_options→recipes;get_balance/get_topup_url/link→wallet;suggest_image_prompt/suggest_music_prompt→suggest_prompt({kind});get_price→get_result(pre-confirm price breakdown). If a schema-vs-docs diff shows one of the old names missing from the live catalog, that's the consolidation — not drift.
Where to look
The MCP server publishes its tool catalog via the standard MCP tools/list request. Claude Code already calls this on connect — the tool definitions are available in the client's MCP state.
To inspect what was returned:
-
List the tools Claude Code currently sees:
/mcp poppifyThat shows the names, but not the param shapes.
-
For the param shapes, ask the deployed server directly via JSON-RPC
tools/listat the canonical MCP endpoint (https://poppify.ai/api/mcp, POST — the Poppify server is stateless, no initialize handshake needed):curl -s https://poppify.ai/api/mcp \ -H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' \ | sed -n 's/^data: //p' | jq '.result.tools[] | select(.name=="apply_session_patch") | .inputSchema'
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.
- 9d ago First seen · 65 lines · 0 tokens per session scan A 3b1e1d6a18a6
poppify-schema-introspect is a skill published in the GitHub repository Poppify/poppify-claude-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 1,252 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
de-vibe
Audit and fix the tells that software was vibe-coded / AI-generated, then give it a small distinctive identity, so it ships looking handcrafted and professional. Use whenever the user says "de-vibe", "does this look AI-generated / vibe coded?", "make this look shippable / handcrafted / professional", "remove the AI…
debug
Interactive debugging workflow with hypothesis-driven probe loop. Use when: unknown bugs, script errors, silent failures, troubleshooting. Not for: known bugs (use bug-fix), GitHub issue analysis (use issue-analyze), code understanding (use code-explore). Output: debug report with probe journal + root cause + fix.
git-investigate
Git history investigation. Use when: tracking code changes, finding where bugs were introduced, root cause analysis. Not for: code exploration (use code-explore), issue analysis (use issue-analyze). Output: history trace + root cause report.
analyze
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots. Use whenever the user asks "how does X work", "map the Y flow", "what are the business rules for Z", "trace the auth path", "explore the codebase…