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/linuxfoundation/lfx-self-serve/paginationnpx skills add linuxfoundation/lfx-self-serve --skill paginationgit clone --depth 1 https://github.com/linuxfoundation/lfx-self-serveWrote 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/linuxfoundation/lfx-self-serve/pagination)<a href="https://agentmods.dev/skills/linuxfoundation/lfx-self-serve/pagination"><img src="https://agentmods.dev/badge/skills/linuxfoundation/lfx-self-serve/pagination.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.00080 | $0.00579 |
| Opus 5 | $0.00040 | $0.00290 |
| Sonnet 5 | $0.00016 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
pagination 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 5d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self Serve Pagination Skill
You are building or modifying a Self Serve backend endpoint that returns a list of resources. All list endpoints use cursor pagination through the query service.
When to use
- A new endpoint returns a list (a
GET /api/<resource>that wraps the query service). - An existing list endpoint needs filtering, sorting, search (typeahead), or tag matching.
- The frontend needs every page of a resource (admin export, full-list aggregation) — use
fetchAllQueryResources. - A list endpoint accidentally uses
limitinstead ofpage_size(canonical bug).
Workflow
- Re-read
docs/architecture/backend/pagination.md(the reference linked below). It documentsQueryServiceResponse<T>,PaginatedResponse<T>, the parameter set, andfetchAllQueryResources. - Use
page_size, NOTlimit. Query-service convention. Exception: the meetings API upstream useslimit— verify against the upstream contract viagh apibefore assuming. - Use
page_tokenfor cursor pagination. Conditional spread:...(pageToken ? { page_token: pageToken } : {}). - Wrap responses in
PaginatedResponse<T>—{ data: T[], page_token?: string }. - Use the
filtersarray format —field:value, auto-prefixed withdata.by the query service. See the doc. - For all-pages fetches, use
fetchAllQueryResources(inhelpers/). Never hand-roll awhile (page_token)loop. - Run the upstream-contract check before shipping — proxy endpoints must align with the upstream schema. Surface "manual validation required" if the upstream cannot be reached.
Reference
docs/architecture/backend/pagination.md— the canonical pagination architecture doc. Treat this as the source of truth; do not maintain a separate copy under this skill.
Scope boundaries
- This skill does NOT cover frontend infinite-scroll UI (see
.claude/skills/self-serve-dev/references/frontend-code-generation.mdSection 4). - It does NOT cover query-service implementation itself — that work routes to
lfx-v2-query-service.
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.
- 5d ago First seen · 36 lines · 80 tokens per session scan A 34f109fe5c88
pagination is a skill published in the GitHub repository linuxfoundation/lfx-self-serve (11 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 579 once invoked, about $0.0004 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…