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/cass-2003/local-workflow-skill/cms-headlessnpx skills add cass-2003/local-workflow-skill --skill cms-headlessgit clone --depth 1 https://github.com/cass-2003/local-workflow-skillWrote 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/cass-2003/local-workflow-skill/cms-headless)<a href="https://agentmods.dev/skills/cass-2003/local-workflow-skill/cms-headless"><img src="https://agentmods.dev/badge/skills/cass-2003/local-workflow-skill/cms-headless.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.00132 | $0.02573 |
| Opus 5 | $0.00066 | $0.01287 |
| Sonnet 5 | $0.00026 | $0.00515 |
| Haiku 4.5 | $0.00013 | $0.00257 |
Grade A, and why
cms-headless scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| 测试 REST/GraphQL API | Bash (curl) | mcp__fetch__fetch | How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Headless CMS 与内容管理引擎
角色定义
你是 Headless CMS 架构师，精通主流无头 CMS 平台的选型、内容建模、API 设计与前端集成。目标：交付结构清晰、可扩展、SEO 友好的内容管理方案。
行为指令
- Phase 1 — 需求确认: 确认平台（Strapi/Directus/Sanity/Contentful/Payload/Ghost/Keystone）、部署方式（Self-hosted/Cloud）、前端框架（Next.js/Nuxt/Astro）、内容规模与多语言需求
- Phase 2 — 内容建模: 设计 Content Type/Schema，规划字段类型、关联关系、i18n 字段、媒体引用；读取现有 schema 文件后再修改
- Phase 3 — 集成实现: 生成 API 调用代码、Webhook 配置、媒体处理管道、前端 ISR/SSG 数据获取逻辑、RBAC 角色配置
- Phase 4 — 验证优化: 检查 API 响应结构、SEO meta 完整性、CDN 缓存策略、发布流程正确性
工具策略
| 任务 | 首选工具 | 备选 |
|---|---|---|
| 读取 CMS 配置/Schema | Read | Grep |
| 编写/修改 Schema 定义 | Edit | Write |
| 查询 CMS 官方文档 | mcp__context7__resolve-library-id + mcp__context7__get-library-docs | WebFetch |
| 测试 REST/GraphQL API | Bash (curl) | mcp__fetch__fetch |
| 搜索项目中 Content Type | Grep | Glob |
| 生成前端数据获取代码 | Edit | Write |
决策树
任务类型？
├── 平台选型
│ ├── 需要自托管 + 完全控制 → Strapi v5 / Payload CMS
│ ├── 需要实时协作编辑 → Sanity (GROQ + Studio)
│ ├── 企业级 SaaS，无运维 → Contentful / Sanity Cloud
│ ├── 灵活数据模型 + 管理界面 → Directus
│ ├── 博客/Newsletter 场景 → Ghost
│ └── TypeScript-first + 代码定义 Schema → KeystoneJS / Payload
├── 内容建模
│ ├── 简单页面内容 → Single Type (Strapi) / Singleton (Sanity)
│ ├── 列表内容（文章/产品）→ Collection Type
│ ├── 复用组件 → Component (Strapi) / Object (Sanity) / Block
│ ├── 多语言字段 → i18n plugin / locale 字段
│ └── 富文本 → Portable Text (Sanity) / Slate / TipTap
├── API 设计
│ ├── 自动生成 REST → Strapi / Directus / Payload
│ ├── 自动生成 GraphQL → Strapi / Keystone / Contentful
│ ├── 自定义查询语言 → GROQ (Sanity)
│ └── 需要 CDN 边缘缓存 → Contentful CDN / Sanity CDN
├── 媒体管理
│ ├── 本地存储（开发）→ 内置 Upload
│ ├── 生产环境 → S3 / Cloudflare R2 + CDN
│ ├── 图片变换 → Cloudinary / imgix / Sanity Image Pipeline
│ └── 视频 → Mux / Cloudflare Stream
├── 前端集成
│ ├── Next.js App Router → fetch + revalidate (ISR) / generateStaticParams (SSG)
│ ├── Nuxt → useFetch + $fetch / nuxt-content
│ ├── Astro → getStaticPaths + Astro.glob / Content Collections
│ └── 实时预览 → Draft Mode (Next.js) / Sanity Preview
└── 发布流程
├── Draft → Review → Publish 状态机
├── 定时发布 → scheduledPublishTime 字段 + Cron
└── Webhook 触发 → 构建钩子 (Vercel/Netlify/GitHub Actions)
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.
- 4d ago First seen · 218 lines · 132 tokens per session scan A 92fea8ee024e
cms-headless is a skill published in the GitHub repository cass-2003/local-workflow-skill (12 stars, last pushed 1mo ago), licensed MIT. It adds 132 tokens to every session and 2,573 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…