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 ssssota/chapplin --skill chapplin-mcp-app-buildergit clone --depth 1 https://github.com/ssssota/chapplinWrote 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/ssssota/chapplin/chapplin-mcp-app-builder)<a href="https://agentmods.dev/skills/ssssota/chapplin/chapplin-mcp-app-builder"><img src="https://agentmods.dev/badge/skills/ssssota/chapplin/chapplin-mcp-app-builder/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/ssssota/chapplin/chapplin-mcp-app-builder"><img src="https://agentmods.dev/badge/skills/ssssota/chapplin/chapplin-mcp-app-builder.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.00077 | $0.00531 |
| Opus 5.5 | $0.00031 | $0.00212 |
| Sonnet 5.5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00008 | $0.00053 |
Grade A, and why
chapplin-mcp-app-builder 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chapplin MCP App Builder
Overview
Use this skill to extend an existing create-chapplin project with new MCP App-enabled tools while preserving template conventions and minimal diffs.
Quick Workflow
- Confirm the project matches the baseline in
references/project-baseline.md. - Detect the framework target from
vite.config.tsandchapplin({ target }). - Implement
defineToolfirst, then implementdefineApp<typeof tool>. - Import
useAppfromchapplin/<target>only when host actions are needed. - Put machine-facing data in
structuredContentand UI-only payload in_meta. - Validate with dev preview and tool-call/UI rendering checks.
Framework/Runtime Selection Rule
- Read
vite.config.ts. - Resolve
targetfromchapplin({ target: "..." }). - Follow
references/framework-deltas.mdfor plugin, JSX runtime, anduseAppimport mapping. - Keep existing style patterns in the same target template.
Implementation Guardrails
- Do not edit generated artifacts such as
dist/,.chapplin/types, or other build outputs. - Do not change HTTP/STDIO transport structure in
src/index.tsunless explicitly requested. - Keep diffs focused on the requested tool/app behavior.
- Match existing naming, schema style, and JSX conventions in the current project.
Validation Checklist
- Run
npm run devand open the chapplin preview UI. - Execute the target tool once and confirm UI renders expected state.
- Confirm initial empty state is handled (
props.outputmay be undefined before first result). - Run project checks (typically
npm run buildand any local test/check scripts). - Re-check framework-specific assumptions against
references/framework-deltas.md.
Reference File Map
- Baseline project shape and registration flow:
references/project-baseline.md - Target-specific runtime differences:
references/framework-deltas.md - Reusable implementation patterns:
references/implementation-recipes.md - Common failures and fixes:
references/troubleshooting.md
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 49 lines · 77 tokens per session scan A a4f19bf0b419
chapplin-mcp-app-builder is a skill published in the GitHub repository ssssota/chapplin (16 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 531 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
incident-response-skill
A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.
skmtc-debug
Diagnose failures in Skmtc sessions — no output, wrong output, error messages, failed bundle builds, parseIssues, "Registered definition mismatch", ref cycles, "Module not found" in generated code, or any other broken behavior. Applies across both CLI usage and generator authoring contexts. Use this skill when the…
pipes-sdk
Build, configure, deploy, and troubleshoot durable blockchain indexers with the Subsquid Pipes SDK (EVM, Solana, Tron, Bitcoin, Hyperliquid) when Portal MCP or curl previews are insufficient for backfills, recurring syncs, joins, app-owned data, or production analytics.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).
debug-tunnel-network
Diagnose Local Coding Agent tunnel, DNS, TCP, TLS, proxy, organization, and office-network blocking issues.
customer-doctor
Diagnose a broken customer install and produce a redacted support report the customer can send back.