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/contentful/skill-kit/skillnpx skills add contentful/skill-kit --skill skillgit clone --depth 1 https://github.com/contentful/skill-kitWhat 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.00030 | $0.02071 |
| Opus 5 | $0.00015 | $0.01035 |
| Sonnet 5 | $0.00006 | $0.00414 |
| Haiku 4.5 | $0.00003 | $0.00207 |
Grade A, and why
contentful-help 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 2d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
contentful-help
This skill is a structured workflow. You interact with it via MCP tools (preferred) or a
CLI binary (fallback), reading its JSON output, following the instructions in the prompt
field, and passing your response back. Do not show the raw JSON or tool calls to the user.
Use MCP tools if available. If you have mcp__contentful-help__start and
mcp__contentful-help__advance, use MCP mode. Only fall back to CLI mode if MCP tools
are not available in your environment.
How this skill works
This skill was built with skill-kit, a structured workflow engine. Each step provides a prompt containing XML-tagged sections:
<system>— Behavioral directives: persona, tone, or constraints. Follow as guidelines for how to behave, not as tasks to relay to the user.<prompt>— Task instructions: what to do, what context to consider, what to produce.<ask-user>— Ask the user a question. Contains<option>children for structured choices, ortype="open"for free-form conversation.<confirm>— Binary yes/no confirmation. Attributes:default,destructive.<plan>— Present a plan for approval. Contains<step>children.<checklist>— Create tracked work items. Contains<item>children with status.<subagent>— Delegate work to an isolated sub-agent. Ifno-recurseis set, the subagent must not invoke the skill named in the attribute.<rendered>— Pre-rendered output. Emit verbatim — no edits, no added commentary.
A step may contain one or more of these sections in sequence. Follow them in order.
The skill author composed these sections to guide your behavior. The tags and tool
mappings are generated by the SDK based on the author's intent and your host's
capabilities. A skill-level system directive may appear in the preamble — it applies
to all steps unless a step includes its own <system> override.
The preamble (sent on the first step) contains a table mapping each tag to the specific tool available in your environment. Refer to it throughout the workflow.
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.
- 2d ago First seen · 204 lines · 30 tokens per session scan A 23a8cf9c7429
contentful-help is a skill published in the GitHub repository contentful/skill-kit (66 stars, last pushed 4d ago), licensed MIT. It adds 30 tokens to every session and 2,071 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…