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/moonbasenpx skills add Generous-Corp/pulp --skill moonbasegit 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/moonbase)<a href="https://agentmods.dev/skills/generous-corp/pulp/moonbase"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/moonbase.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.00086 | $0.02421 |
| Opus 5 | $0.00043 | $0.01210 |
| Sonnet 5 | $0.00017 | $0.00484 |
| Haiku 4.5 | $0.00009 | $0.00242 |
Grade A, and why
moonbase 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Moonbase Skill
Use this when adding, building, or testing license activation / copy protection
in a Pulp plugin or app with Moonbase,
or when working under examples/moonbase-activation/.
Moonbase is a hosted licensing service. moonbase-cpp is a header-only,
MIT-licensed C++17 client. Pulp consumes it via FetchContent (target
moonbase::licensing) — no fork, no vendoring. Pulp owns only a registry entry,
docs, this skill, and the reference example; upstream owns the SDK.
Load-bearing build settings (lead with these)
pulp add moonbase resolves the dependency and the link target, but it does
not carry the two cache settings below. Set them before the dependency is
made available:
set(MOONBASE_BUILD_TESTS OFF CACHE BOOL "" FORCE)
set(MOONBASE_BUILD_EXAMPLES OFF CACHE BOOL "" FORCE)
set(MOONBASE_USE_CURL OFF CACHE BOOL "" FORCE) # supply your own transport
target_link_libraries(MyPlugin PRIVATE moonbase::licensing)
MOONBASE_USE_CURL=OFF makes the upstream INTERFACE target define
MOONBASE_DISABLE_CURL_TRANSPORT for you and drops libcurl. Inject a transport
instead — the example supplies one over Pulp's cpp-httplib/mbedTLS stack.
OpenSSL bolt-on (known upstream caveat)
Moonbase documents OpenSSL as a system requirement (its README expects
OpenSSL::SSL/OpenSSL::Crypto findable on the system), and v3.3.0's CMake runs
find_package(OpenSSL REQUIRED) and links it unconditionally, with no
MOONBASE_CRYPTO_NATIVE CMake wiring. So OpenSSL must be present at configure
time, and v1 simply uses the OpenSSL crypto backend (required + linked anyway) —
the simplest, no-extra-wiring path. This is upstream's intended design, not a
blocker and not a reason to fork. The example's CMake auto-discovers OpenSSL;
per platform:
- macOS:
brew install openssl@3(/opt/homebrew/opt/openssl@3on Apple silicon); pass-DOPENSSL_ROOT_DIR=$(brew --prefix openssl@3)if needed. - Linux:
apt install libssl-dev(or distro equivalent). - Windows: vcpkg (
vcpkg install openssl) or a system package, discoverable via the toolchain /OPENSSL_ROOT_DIR.
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 · 197 lines · 86 tokens per session scan A e568c830fa32
moonbase is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 2,421 once invoked, about $0.0004 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…