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.
git clone --depth 1 https://github.com/textura-agency/next16-claude-starterWrote 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/commands/textura-agency/next16-claude-starter/new-page)<a href="https://agentmods.dev/commands/textura-agency/next16-claude-starter/new-page"><img src="https://agentmods.dev/badge/commands/textura-agency/next16-claude-starter/new-page/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/commands/textura-agency/next16-claude-starter/new-page"><img src="https://agentmods.dev/badge/commands/textura-agency/next16-claude-starter/new-page.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.00000 | $0.00481 |
| Opus 5.5 | $0.00000 | $0.00192 |
| Sonnet 5.5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
new-page 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 1mo 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.
What it actually says
Implement a page or section: $ARGUMENTS
Follow obsidian/workflows/new-page.md. If a Figma URL was given, use the
figma-to-section skill for extraction and asset handling.
- Read first —
obsidian/workflows/ai-agent-guide.mdfor the hard rules, then the topic notes you actually need (design-system.mdfor styling,animation-system.md+text-engine.mdfor motion,component-conventions.mdfor placement,html-semantics.mdfor markup). If the project is otherwise empty, build insrc/views/home.tsxon/rather than scaffolding a new route. - Plan the route —
app/<route>/page.tsx, ~3 lines, delegates to a view. Add the route tosrc/app/sitemap.tsin the same change. - Build the view in
src/views/<page>.tsx, composed of components. Reusecomponents/ui/andcomponents/common/before creating anything new. - Tokens before styles. Any new colour/spacing/type/radius value becomes a
Tier 1 primitive + Tier 2 semantic token in
globals.css, commented with its origin. Nothing hardcoded. - Motion via springs — the right primitive for each need, semantic
tag. - Content via props/hooks. Mocks under
src/data/mocks/<page>.ts. Async data gets loading/error/empty states. - Server-first —
"use client"only at leaves. - Assets to
public/assets/<section>/, referenced by absolute path. - Verify — run the
qa-verifyskill (script + judgement checks) and fix until clean. - Document — update the catalog notes for anything new, add a changelog entry, and an ADR if you made an architectural choice.
Report: files created, new tokens and why, values that could not map to tokens (flag for design review), assumptions made.
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.
- 1mo ago First seen · 36 lines · 0 tokens per session scan A f1b370e9d56b
new-page is a command published in the GitHub repository textura-agency/next16-claude-starter (139 stars, last pushed 13d ago), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 481 tokens. 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 commands, from other repositories
profile
Save, load, inspect, update, reset, or delete diagram-design client profiles.
erne-animate
ERNE — Implement animations using the ui-designer agent with Reanimated and Gesture Handler.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
responsive-design-specialist
Use when a layout breaks between sizes. Arbitrary breakpoints, type that does not scale, images that blow out the grid, or a desktop design retrofitted onto mobile.
design-audit
Audit the rendered design of live sites. Evidence capture first, then one critique per site. Argument is a URL, a repo name, or all.
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.