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 skills/generous-corp/pulp/androidnpx skills add Generous-Corp/pulp --skill androidgit clone --depth 1 https://github.com/Generous-Corp/pulpWrote 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/generous-corp/pulp/android)<a href="https://agentmods.dev/skills/generous-corp/pulp/android"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/android.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.12613 |
| Opus 5 | $0.00030 | $0.06306 |
| Sonnet 5 | $0.00012 | $0.02523 |
| Haiku 4.5 | $0.00006 | $0.01261 |
Grade A, and why
android 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 today.
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 — 1,161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Skill
Build, deploy, and debug Pulp on Android. This skill captures the architecture decisions and hard-won gotchas from the Android platform bringup.
Pre-flight: plugin ↔ CLI skew check
Before running pulp doctor android / pulp build / pulp ship for
Android work, source the shared skew-check helper so a user on an
outdated CLI sees a one-line hint (stderr, once per session) before
wrestling with a confusing flag-missing error:
source "$(git rev-parse --show-toplevel)/tools/scripts/cli_version_check.sh"
pulp_cli_version_check
Advisory only. Full release-discovery contract in the upgrade skill.
Architecture Overview
Kotlin (Android UI) C++ (Pulp core)
├── PulpApplication ├── libpulp.so (arm64)
│ └── System.loadLibrary │ ├── core/* subsystems
├── PulpSurfaceView │ ├── Dawn (Vulkan backend)
│ ├── SurfaceHolder.Cb │ ├── Skia Graphite
│ └── onTouchEvent ──JNI──→│ └── Oboe audio
├── PulpActivity │
├── PulpAudioService └── gpu_surface_android.cpp
└── PulpMidiService ├── Surface lifecycle
├── Touch → View routing
└── Widget hierarchy
Key Files
| File | Purpose |
|---|---|
tools/cmake/PulpAndroid.cmake |
NDK toolchain integration, Oboe, platform wiring |
core/render/platform/android/gpu_surface_android.cpp |
Vulkan surface, touch routing, widget hierarchy |
android/app/src/main/kotlin/com/pulp/render/PulpSurfaceView.kt |
SurfaceView + touch dispatch |
android/app/src/main/kotlin/com/pulp/PulpApplication.kt |
JNI load, lifecycle |
core/platform/src/android/jni_bridge.cpp |
JNI_OnLoad, class caching, exception guards |
tools/build-skia-android.sh |
Skia Graphite + Dawn arm64 build script |
Branch & Worktree
Android work lives on feature/android-targeting, typically in a worktree at ../pulp-android:
# Create worktree (if not already present)
git worktree add ../pulp-android feature/android-targeting
# Always work in the worktree, not the main repo
cd ../pulp-android
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.
- today First seen · 1,161 lines · 59 tokens per session scan A 70abe49d2e8a
android is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 12,613 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…