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/contrib-intakenpx skills add Generous-Corp/pulp --skill contrib-intakegit 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/contrib-intake)<a href="https://agentmods.dev/skills/generous-corp/pulp/contrib-intake"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/contrib-intake.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.00075 | $0.02507 |
| Opus 5 | $0.00037 | $0.01254 |
| Sonnet 5 | $0.00015 | $0.00501 |
| Haiku 4.5 | $0.00007 | $0.00251 |
Grade A, and why
contrib-intake 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 — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taking in an outside contribution
The contributor's half is the contribute skill. This
is the other half: what you do when their work arrives.
The whole job is getting contributed commits onto an in-repo branch that can obtain the required checks, then treating it like any other PR.
Why an in-repo branch, and not just merging their fork PR
main requires these checks (gh api repos/Generous-Corp/pulp/branches/main/protection):
macos · Enforce version & skill sync · Build + prove + (owner-gated) deploy
Vellum trusted freeze · Vellum freeze
macos is posted by the self-hosted Mac Studios, and one required check is
owner-gated by name. A pull request from a fork:
- runs with a read-only token and no secrets,
- needs manual approval before any workflow starts,
- and would execute contributor code on your own machines if approved.
There is no precedent to rely on — as of 2026-07-29 this repo has had zero PRs from a fork, so that path has never once obtained these checks. Do not discover whether it works while trying to land someone's contribution.
So: a fork PR (or an issue, or a bundle in a message) is a fine delivery
mechanism. It is not the thing you merge. Adopt it into contrib/<topic> in
this repo and ship that.
Before anything else: two rules that come before every step below
Rule 0 — read the whole diff before you run anything from the patched tree.
contributor_check.sh executes gates.sh, which executes other scripts under
tools/scripts/ from the tree you just applied their patches to. So "just run
the check first" is arbitrary code execution on your machine, before any human has
read a line. Read the diff first, and read these paths with real attention:
git -C /tmp/adopt diff <base>..HEAD --stat
git -C /tmp/adopt diff <base>..HEAD -- tools/ hooks/ .githooks/ .github/ '*.cmake' CMakeLists.txt
A contribution that only touches core/** and test/** is the easy case. Anything
touching build, hook, workflow, or script surfaces is the case this rule exists for.
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 · 228 lines · 75 tokens per session scan A cf26369f948e
contrib-intake is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 2,507 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…