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-analyticsgit 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-analytics)<a href="https://agentmods.dev/skills/textura-agency/next16-claude-starter/payload-analytics"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/payload-analytics/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-analytics"><img src="https://agentmods.dev/badge/skills/textura-agency/next16-claude-starter/payload-analytics.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00169 | $0.01416 |
| Opus 5.5 | $0.00068 | $0.00566 |
| Sonnet 5.5 | $0.00034 | $0.00283 |
| Haiku 4.5 | $0.00017 | $0.00142 |
Grade A, and why
payload-analytics 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 10d 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.
- `curl -X POST …/api/track -H 'dnt: 1' …` → `counted: false`; a bot UA → `false`; How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics in the admin
What an owner wants from "light analytics": how many people came, what they
read and for how long, where from, on what — in the admin they already use.
What they must not get: a third-party script on the page, a cookie, or a
promise in the privacy policy the site doesn't keep. Kit:
bash .claude/skills/payload-cms/scaffold.sh analytics (needs core + admin).
Decisions — and why
| # | Decision | Why |
|---|---|---|
| A1 | Self-hosted in the CMS's Postgres (page-views, hidden from the nav), read with plain SQL (readStats) |
No vendor, no script, no dependency; the data sits beside the content it describes |
| A2 | Only with consent: the beacon fires only when consent.analytics === true |
The cookie banner's analytics switch must mean something — and the privacy policy promises it |
| A3 | /api/track drops bots (UA regex incl. Lighthouse/headless/monitors), /admin + /api paths, DNT and GPC |
Counts people, not crawlers or the editor; honours "do not track" even with consent |
| A4 | No personal data kept: visitor = sha256(PAYLOAD_SECRET + day + IP + UA) truncated; IP and UA never stored; no cookie of our own |
One person = one visitor per day, unlinkable across days. "Visitors" over a range = sum of daily visitors (what privacy-first tools call visits) |
| A5 | Time on page = visible time, banked across visibility changes, sent once on leave (pagehide / hidden / route change), capped at 30 min, written only by the same day-hash, only once |
A background tab doesn't inflate it; the id can't be used to rewrite other rows. Views with no clean leave are excluded from the average, not counted as 0 |
| A6 | Country from the edge header (x-vercel-ip-country / cf-ipcountry), else the Accept-Language region flagged countryApprox and footnoted |
Exact on the host, honest locally |
| A7 | Retention = the privacy policy's figure (default 14 months), swept on ~1 % of writes | The policy and the database agree, with no cron |
| A8 | Server-rendered view; the chart is one client leaf — plain SVG, no chart library, no animation; hover is a discrete state | No dependency, no motion-rule exception; lists are plain HTML |
| A9 | Countries as a code badge + English name (Intl.DisplayNames) |
Windows draws flag emoji as bare letters |
| A10 | Bounce rate = visitor-days with one view; every KPI compared with the previous period, colour by better/worse (bounce inverted) | The four numbers an owner asks about, with direction |
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.
- 10d ago First seen · 68 lines · 169 tokens per session scan A c694410b8e1f
payload-analytics is a skill published in the GitHub repository textura-agency/next16-claude-starter (137 stars, last pushed 3d ago), licensed Unlicense. It adds 169 tokens to every session and 1,416 once invoked, about $0.0007 per session on Opus 5.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-10-08.
Other skills, from other repositories
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…
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…
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…