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/tryghost/ghost/shade-page-templatesnpx skills add TryGhost/Ghost --skill shade-page-templatesgit clone --depth 1 https://github.com/TryGhost/GhostWrote 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/tryghost/ghost/shade-page-templates)<a href="https://agentmods.dev/skills/tryghost/ghost/shade-page-templates"><img src="https://agentmods.dev/badge/skills/tryghost/ghost/shade-page-templates.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.00044 | $0.00957 |
| Opus 5 | $0.00022 | $0.00478 |
| Sonnet 5 | $0.00009 | $0.00191 |
| Haiku 4.5 | $0.00004 | $0.00096 |
Grade A, and why
Shade page templates 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 4d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shade — page templates
When building a new admin page, the first question is what page type is this? — then reach for the matching pattern instead of inventing chrome.
Page type taxonomy
List page
Browsing or scanning a collection of items.
- Live examples: Members, Tags, Comments, Automations, ActivityPub.
- Chrome shape:
PageHeader(title + count + search/filter/actions) → table or list → empty state → pagination. - Pattern:
ListPage(composesPageHeader). Heavy filter UI usesFilters.
Detail page
Working with a single item — viewing, editing, or both.
- Live examples: Post editor.
- Chrome shape:
PageHeaderwith breadcrumb + title + meta, a primary action area, and a content area dedicated to the item. - Pattern: not built this milestone. Use
PageHeaderdirectly and lay out the body yourself.
Settings
Out of scope for the current page-template milestone. Don't force a settings page into ListPage or PageHeader.
Workflow / multi-step flows
No standard yet — too few examples. Don't standardise prematurely.
Canonical list page skeleton
import {ListPage} from '@tryghost/shade/page-templates';
import {PageHeader, ViewBar, FilterBar} from '@tryghost/shade/patterns';
import {Button, EmptyIndicator, Table} from '@tryghost/shade/components';
<ListPage>
<ListPage.Header>
{/* sticky={false} — ListPage.Header owns stickiness and blur */}
<PageHeader sticky={false} blurredBackground={false}>
<PageHeader.Left>
<PageHeader.Title>
Members<PageHeader.Count>{count}</PageHeader.Count>
</PageHeader.Title>
</PageHeader.Left>
<PageHeader.Actions>
<PageHeader.ActionGroup>
<Button>Add member</Button>
</PageHeader.ActionGroup>
</PageHeader.Actions>
</PageHeader>
<ViewBar>{/* optional */}</ViewBar>
<FilterBar>{/* optional — auto-collapses when empty */}</FilterBar>
</ListPage.Header>
<ListPage.Body>
{items.length === 0 ? <EmptyIndicator title='No members yet' /> : <Table>...</Table>}
</ListPage.Body>
</ListPage>
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.
- 4d ago First seen · 99 lines · 44 tokens per session scan A 032a1f7e8cef
Shade page templates is a skill published in the GitHub repository TryGhost/Ghost (55,149 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 957 once invoked, about $0.0002 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
cms-metadata-tagger
Takes a finished piece of content and produces a complete, archive-ready metadata record — including descriptive tags, subject classifications, rights notes, and an archival summary — for entry into a content management or digital archive system.
cms-metadata-writer
Writes structured metadata fields — title tag, meta description, tags, category, slug, and Open Graph text — for a CMS entry, optimized for search discoverability and social sharing.
intlayer-content
Define rich content structures using Intlayer content nodes. Use when the user asks to "create translations", "handle pluralization", "use markdown in content", or implement "conditional content".
intlayer-angular
Integrates Intlayer internationalization with Angular applications. Use when the user asks to "setup Angular i18n", create a new translated component, use the "useIntlayer" composable, or configure providers.
intlayer-next-js
Integrates Intlayer internationalization with Next.js App Router and Pages Router. Use when the user asks to "setup Next.js i18n", use "useIntlayer" in Server Components, or handle client-side translations in Next.js.
intlayer-react
Integrates Intlayer internationalization with React component. Use when the user asks to "setup React i18n", create a new translated component, use the "useIntlayer" hook, or configure providers.