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/heritage-profilenpx skills add Generous-Corp/pulp --skill heritage-profilegit 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/heritage-profile)<a href="https://agentmods.dev/skills/generous-corp/pulp/heritage-profile"><img src="https://agentmods.dev/badge/skills/generous-corp/pulp/heritage-profile.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.00064 | $0.02304 |
| Opus 5 | $0.00032 | $0.01152 |
| Sonnet 5 | $0.00013 | $0.00461 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
heritage-profile 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heritage Profile Authoring
Create evidence-backed sampler character as portable profile data. Keep the runtime profile neutral and the research record separate. Never require access to a private artifact repository.
Before authoring, read the current Pulp Sample Heritage guide and run:
pulp audio heritage --help
Read references/profile-format.md whenever selecting blocks, importing/exporting, or handling a schema version. Copy assets/profile-template.json as the starting profile. Copy assets/artifact-manifest-template.json into the caller-selected artifact directory or repository.
Workflow
-
Choose caller-owned locations. Ask for or infer a working directory for the profile and a separate archive directory or repository for research, prompts, reports, rendered audio, and hashes. Do not default to any Pulp maintainer's private repository. A private overlay skill may supply these paths, but the workflow must also work without that overlay.
-
Describe the target neutrally. Write audible and mechanical goals such as “gritty low-rate percussion with clock-linked pitch and a dark output” before researching a named reference. Use a
neutral.*profile ID composed only of lowercase ASCII letters, digits, dots, and hyphens. Do not put a company, product, model, or other mark in the ID. -
Research cleanly. Prefer legally accessible primary or technical sources: owner and service manuals, schematics, patents, converter data sheets, standards, and published technical papers. A personally controlled capture is optional evidence when its provenance and right to use are recorded. Do not inspect proprietary source, decompiled firmware, leaked material, or another emulator's implementation. Do not copy source material wholesale into the archive.
-
Record evidence before choosing values. For every researched value, record the exact profile field, value or range, source kind, full citation, page/figure/section locator, access date, use or license basis, and confidence as
confirmed,probable, ortest. Keep inference distinct from a source's explicit claim. Record unresolved values astest; do not invent precision.
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.
- today First seen · 204 lines · 64 tokens per session scan A 8d0df2f4977c
heritage-profile is a skill published in the GitHub repository Generous-Corp/pulp (16 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 2,304 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…