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 Dragoon0x/canon --skill canon-paginationgit clone --depth 1 https://github.com/Dragoon0x/canonWrote 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/dragoon0x/canon/canon-pagination)<a href="https://agentmods.dev/skills/dragoon0x/canon/canon-pagination"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-pagination/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/dragoon0x/canon/canon-pagination"><img src="https://agentmods.dev/badge/skills/dragoon0x/canon/canon-pagination.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.00096 | $0.02113 |
| Opus 5.5 | $0.00038 | $0.00845 |
| Sonnet 5.5 | $0.00019 | $0.00423 |
| Haiku 4.5 | $0.00010 | $0.00211 |
Grade A, and why
canon-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 2mo 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CANON · Pagination
Long lists need traversal. Pick the pattern to match the task, not the fashion.
The three patterns
| Pattern | Use when |
|---|---|
| Pagination (numbered pages) | Users compare, revisit, bookmark, or share specific positions |
| Infinite scroll | Feed-style discovery where "what's next" is primary (social, news) |
| Load more (button) | Discovery with control — user decides when to fetch more |
| Virtualized list | 10,000+ items where semantics matter (tables, ordered lists) |
Default: pagination for task-oriented UIs (search results, tables, admin lists). Infinite scroll is a feed pattern, not a universal answer.
Why pagination beats infinite scroll for most apps
- Position is addressable — users can bookmark page 5, share a URL, return to where they were.
- The footer is reachable — infinite scroll eats footers.
- Users know when they're done — "Page 12 of 47" gives a clear scale.
- Browser back button works — infinite scroll loses scroll position on navigation.
- Screen readers — paginated pages announce completion.
Infinite scroll wins for: Twitter-style feeds, image galleries, TikTok-style single-item-at-a-time.
Pagination layout
Two patterns, both valid:
Numbered pages
← 1 2 3 … 47 48 49 →
- Show: first page, last page, current page, two neighbors on each side.
- Ellipsis between gaps.
- Prev/Next arrows bracket the numbers.
- Current page visually distinct (filled, disabled, not a link).
Simple prev/next with position
Showing 21–40 of 934 ← Previous | Next →
- Position text is always visible.
- Prev disabled on page 1. Next disabled on last page.
- Works when page count is unknown (live data).
Use numbered pagination when the total is known; use simple prev/next when it isn't.
Sizing
| Element | Value |
|---|---|
| Button height | 36–40px |
| Button min-width | 36–40px (square for numbers) |
| Gap between buttons | 2–4px |
| Horizontal padding | 8–12px |
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.
- 2mo ago First seen · 254 lines · 96 tokens per session scan A e64f213ebc50
canon-pagination is a skill published in the GitHub repository Dragoon0x/canon (6 stars, last pushed 6mo ago), licensed MIT. It adds 96 tokens to every session and 2,113 once invoked, about $0.0004 per session on Opus 5.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-31.
canon-pagination compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| canon-paginationDragoon0x/canon | Skill | 6 | 6mo ago | MIT | A | 96 | Claude Code, Codex |
| accessibilitydiegosouzapw/awesome-omni-skills | Skill | 170 | 4mo ago | MIT | C | 119 | Claude Code, Codex |
| accessibilityericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 86 | Claude Code, Codex |
| Website AuditPramodDutta/qaskills | Skill | 245 | 4d ago | MIT | A | 33 | Claude Code, Codex |
| huawei-cloud-cts-trace-managementhuaweicloud/huaweicloud-devkit | Skill | 70 | yesterday | Apache-2.0 | A | 249 | Claude Code |
| accessibility-auditoyi77/1ai-skills | Skill | 17 | yesterday | MIT | A | 29 | Claude Code |
| a11y-auditgreglas75/zuvo | Skill | 7 | 3d ago | MIT | A | 147 | Claude Code |