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 romshark/datapages --skill datapages-actionsgit clone --depth 1 https://github.com/romshark/datapagesWrote 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/romshark/datapages/datapages-actions)<a href="https://agentmods.dev/skills/romshark/datapages/datapages-actions"><img src="https://agentmods.dev/badge/skills/romshark/datapages/datapages-actions/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/romshark/datapages/datapages-actions"><img src="https://agentmods.dev/badge/skills/romshark/datapages/datapages-actions.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.00050 | $0.02377 |
| Opus 5.5 | $0.00020 | $0.00951 |
| Sonnet 5.5 | $0.00010 | $0.00475 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade A, and why
datapages-actions 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 yesterday.
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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Actions
Read datapages first for the build loop, hard rules and naming conventions.
Define a page action as a value-receiver method on its page type. Define an action not tied to a page as a method on *App. Give each action 1 route doc comment. A page action route must be below its page route. For example, /login/submit is valid for PageLogin at /login. An action route cannot end in a {name...} wildcard. Pass that value in a query parameter or a signal.
// POSTSubmit is /login/submit
func (PageLogin) POSTSubmit(r *http.Request) error { return nil }
// POSTSignOut is /sign-out/{$}
func (*App) POSTSignOut(r *http.Request) error { return nil }
GETXXX is a file action, not the page's GET handler. A browser loads it by
URL from a link, image or download. It must return datapages.File and may take
only *http.Request, Session, Path and Query. The generated href package
builds its URL. A GET action skips CSRF checks and must not change server state.
Use a QUERYXXX action for a read that sends data in the body, such as a search with a large filter. It skips the CSRF check because QUERY is a safe method. Never change state in it.
Parameters
Parameters may appear in any order because the generator matches them by type. Names are unrestricted except for stateID. Read wrapped values from .Values.
| type | what |
|---|---|
*http.Request |
required |
datapages.SSE |
patches the stream of the calling page; page actions only, not *App actions |
Session |
the current session, see datapages-sessions |
datapages.Path[struct{...}] |
route variables, path:"id" tags |
datapages.Query[struct{...}] |
query parameters, query:"p" tags |
datapages.Signals[struct{...}] |
signals sent by the client, json:"v" tags |
datapages.State[StateX] |
per-tab server state, see datapages-state |
stateID string |
tab event address; requires State[T], see datapages-state |
datapages.PageCacheWriter |
writes the offline page cache, see datapages-offline |
datapages.Dispatcher[EventX] |
publishes EventX, see datapages-events |
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.
- yesterday Changed · +2 lines 3feffd331cad
- 3d ago Changed b95dcb5b9918
- 4d ago Changed · +3 lines af7766e759ff
- 5d ago Changed · +49 lines · +5 tokens per session 657713cbc4c6
- 8d ago Changed 00ec585999dd
- 12d ago Changed · +2 lines · +2 tokens per session 827dcbfc30af
- 13d ago Changed 76d1fed18fef
- 20d ago Changed · +2 lines 4ac6eff36cad
- 24d ago Changed · +1 lines a72dccb119a8
- 25d ago First seen · 98 lines · 43 tokens per session scan A a1dc0d516c07
datapages-actions is a skill published in the GitHub repository romshark/datapages (114 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 2,377 once invoked, about $0.0002 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-09-20.
Other skills, from other repositories
structpages
Guide for building Go web applications with the structpages framework (struct-based routing + gsx + HTMX). Use when writing routes, pages, page groups, Props methods, handler methods (ServeHTTP), page components, partials, HTMX partial rendering and nested swap levels, URL and element-id generation (the gsx…
pinchtab
Use this skill when a task needs browser automation through PinchTab: open a website, inspect interactive elements, click through flows, fill out forms, scrape page text, reuse a dedicated automation profile with user approval, export screenshots or PDFs, manage multiple browser instances, or fall back to the HTTP API…
printing-press-amend
Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally…
golang-graphql
Implements GraphQL APIs in Golang using gqlgen or graphql-go. Apply when building GraphQL servers, designing schemas, writing resolvers, handling subscriptions, or integrating GraphQL with existing Go HTTP services. Also apply when the codebase imports github.com/99designs/gqlgen or github.com/graph-gophers/graphql-go.
golang-grpc
Provides gRPC usage guidelines, protobuf organization, and production-ready patterns for Golang microservices. Use when implementing, reviewing, or debugging gRPC servers/clients, writing proto files, setting up interceptors, handling gRPC errors with status codes, configuring TLS/mTLS, testing with bufconn, or…
golang-swagger
Golang OpenAPI/Swagger documentation with swaggo/swag — annotation comments (@Summary, @Param, @Success, @Router, @Security), swag init code generation, framework integrations (gin, echo, fiber, chi, net/http), security definitions (Bearer/JWT, OAuth2, API key), and struct tags (swaggertype, enums, example…