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 skills add textura-agency/next16-claude-starter --skill payload-cmsgit clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/textura-agency/next16-claude-starter/payload-cms)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/payload-cms"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/payload-cms/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/payload-cms"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/payload-cms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 14 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.1 | $0.00101 | $0.01998 |
| Opus 5 | $0.00051 | $0.00999 |
| Sonnet 5 | $0.00020 | $0.00400 |
| Haiku 4.5 | $0.00010 | $0.00200 |
Grade A, and why
payload-cms 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 12d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Payload CMS in this starter
Payload is a Next-native CMS: it installs into this app's app/ directory
rather than running as a separate service. The database is Supabase Postgres
(see the supabase-db skill), media goes to Supabase Storage over its
S3-compatible API.
Verified against Payload 3.88.0 (2026-08). Payload 4 is in canary — do not use it here without checking the peer ranges yourself.
0. Pre-flight — three things that break the install
- Next.js version.
@payloadcms/[email protected]peer-requiresnext >=16.2.6 <17. The starter is on16.3.1, which satisfies it — but check, don't assume, since both sides move:
If Next is below the floor, bump it andnode -p "require('./package.json').dependencies.next" npm view @payloadcms/next peerDependencieseslint-config-nexttogether. - ESM.
next.config.tsmust be ESM to wrap withwithPayload. This starter already usesnext.config.tswith ESM syntax — check before assuming. - A Supabase project must exist with both connection strings to hand. Run
the
supabase-dbskill first if it does not.
Confirm the collection list with the user before writing any config. Derive the
proposal from what the site actually renders — read src/views/** and the mock
data in src/data/mocks/ and name real content types, not a generic posts.
1. Install
yarn add payload @payloadcms/next @payloadcms/db-postgres \
@payloadcms/richtext-lexical @payloadcms/storage-s3 graphql sharp
sharp is required for image resizing. graphql is a hard peer dep even if you
never use the GraphQL API.
2. src/payload.config.ts
import path from 'path'
import { fileURLToPath } from 'url'
import { buildConfig } from 'payload'
import { postgresAdapter } from '@payloadcms/db-postgres'
import { lexicalEditor } from '@payloadcms/richtext-lexical'
import { s3Storage } from '@payloadcms/storage-s3'
import sharp from 'sharp'
import { Media } from './collections/media'
import { Pages } from './collections/pages'
const dirname = path.dirname(fileURLToPath(import.meta.url))
export default buildConfig({
admin: {
user: 'users',
importMap: { baseDir: path.resolve(dirname) },
},
collections: [Pages, Media],
editor: lexicalEditor(),
secret: process.env.PAYLOAD_SECRET || '',
typescript: { outputFile: path.resolve(dirname, 'payload-types.ts') },
db: postgresAdapter({
pool: { connectionString: process.env.DATABASE_URL || '' },
// Schema is pushed automatically in dev. In production this must be false —
// ship migrations instead, or a deploy can rewrite the live schema.
push: process.env.NODE_ENV !== 'production',
}),
plugins: [
s3Storage({
collections: { media: true },
bucket: process.env.S3_BUCKET || '',
config: {
endpoint: process.env.S3_ENDPOINT, // https://<ref>.storage.supabase.co/storage/v1/s3
region: process.env.S3_REGION, // e.g. eu-central-1
forcePathStyle: true, // REQUIRED for Supabase
credentials: {
accessKeyId: process.env.S3_ACCESS_KEY_ID || '',
secretAccessKey: process.env.S3_SECRET_ACCESS_KEY || '',
},
},
}),
],
sharp,
})
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.
- 12d ago First seen · 198 lines · 101 tokens per session scan A 42ed9cb4b018
payload-cms is a skill published in the GitHub repository textura-agency/next16-claude-starter (117 stars, last pushed 3d ago), licensed Unlicense. It adds 101 tokens to every session and 1,998 once invoked, about $0.0005 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
azure-postgres-ts
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL…
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
supabase-node
Express/Hono with Supabase and Drizzle ORM.