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 Cratis/AI --skill cratis-arc-query-paginggit clone --depth 1 https://github.com/Cratis/AIWrote 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/cratis/ai/cratis-arc-query-paging)<a href="https://agentmods.dev/skills/cratis/ai/cratis-arc-query-paging"><img src="https://agentmods.dev/badge/skills/cratis/ai/cratis-arc-query-paging.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.1 | $0.00084 | $0.01941 |
| Opus 5 | $0.00042 | $0.00971 |
| Sonnet 5 | $0.00017 | $0.00388 |
| Haiku 4.5 | $0.00008 | $0.00194 |
Grade A, and why
cratis-arc-query-paging 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 today.
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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Page and sort an Arc query
Arc applies paging and sorting for you. You never write Skip/Take or read
the query string — you choose a return shape that the framework can narrow.
Verified product sources
| Package | Version | Purpose |
|---|---|---|
Cratis.Arc.Core |
22.10.4 |
QueryableQueryRenderer, Paging, Sorting, PagingInfo |
Cratis.Arc.MongoDB |
22.10.4 |
Observe helpers that page at the source |
Cratis.Arc.EntityFrameworkCore |
22.10.4 |
DbSet<T> observe helpers that page at the source |
@cratis/arc.react |
22.10.4 |
useWithPaging, useSuspenseWithPaging |
Reverify before claiming support for another version. A small, bounded result
set does not need any of this — IEnumerable<T> is fine.
The wire contract
| Query-string key | Effect |
|---|---|
pageSize |
Required to page at all. Must be greater than 0 |
page |
Zero-based. Defaults to 0 when pageSize is present |
sortby |
Field name; PascalCased before use, so ?sortby=name sorts on Name |
sortDirection |
desc (case-insensitive) sorts descending; anything else, including a missing value, is ascending |
Two consequences that surprise people:
pagealone does nothing. WithoutpageSizethe request is not paged.- Sorting needs both keys.
sortbywithoutsortDirectionis ignored entirely.
Paging is validated before the query runs: page must be >= 0 and pageSize
must be > 0, and a violation comes back as a validation failure rather than a
crash.
Which return shapes page
A query is a public static method on the [ReadModel] type, discovered by its
return type.
| Return | Paged? | How |
|---|---|---|
T, T?, IEnumerable<T>, List<T>, T[] |
No | Nothing narrows the result |
IQueryable<T> |
Yes | The query renderer counts, orders, then applies Skip/Take |
Task<IQueryable<T>> |
Yes | Awaited first, then rendered as the queryable it unwraps to |
ISubject<IEnumerable<T>> |
Yes | Not by the renderer — the storage Observe() helpers read the ambient query context and page at the source, reapplying on every change |
ISubject<IQueryable<T>> |
No | No Observe overload returns it, and the renderer matches on the outer type |
What ships with it
1 file 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.
- today First seen · 174 lines · 84 tokens per session scan A 940c6c55b17e
cratis-arc-query-paging is a skill published in the GitHub repository Cratis/AI (2 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 1,941 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-09-06.
Other skills, from other repositories
add-permission
Add a permission constant across backend and frontend.
gen-types
Regenerate frontend API types from the backend OpenAPI spec.
architecture-paradigm-cqrs-es
Applies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.
new-feature
Scaffold a full-stack feature from entity to frontend page.
regenerate-api
Regenerate the AppointMe frontend API client (orval/TanStack Query hooks + TypeScript schemas) after the backend OpenAPI surface changes. Use this whenever backend endpoints, request/response DTOs, or other contract-affecting types are added, removed, or modified — e.g. after editing files under src/AppointMe.Api…
csharp-skills
Use when developing with .NET/C# for Web APIs, ORM data access, Excel/Word file I/O, spreadsheet controls, error tracking, or .NET code protection. Index of 9 skills: Furion, Admin.NET Backend, Admin.NET Frontend, SqlSugar, NPOI, SOD, ReoGrid, DotNet Reactor, Sentry.