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 commands/alwkala/tidyfactor-design/pagegit clone --depth 1 https://github.com/alwkala/tidyfactor-designWrote 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/alwkala/tidyfactor-design/page)<a href="https://agentmods.dev/commands/alwkala/tidyfactor-design/page"><img src="https://agentmods.dev/badge/commands/alwkala/tidyfactor-design/page.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.00000 | $0.00520 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
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 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command: page — Add a Marketing/Content Page
Purpose
The recurring loop this whole skill exists to support: add another page to the prototype without any risk of visual drift, however large the site grows. This is the command most likely to run dozens of times on one project — its discipline matters more than any other command's.
When to run it
- Any time a new website page (not a dashboard/app screen — see
dashboardfor that) is needed: landing, pricing, about, feature, listing, detail, contact, 404... - User phrasing: "add a pricing page", "build the about page",
page.
What it does
- Confirm
design-system/tokens.cssandcomponents.css(or the foundation's theme) are current — never build against a stale set. - Apply the
references/foundations/<choice>.mdnarrative-quality principles: the hero is a thesis for this page's job, structure encodes real information (no decorative numbering unless it's a real sequence), copy is real content for this page, not lorem ipsum. - Compose the page only from existing
components.cssclasses / daisyUI components / Tailwind utilities per the locked foundation. - Hit a design need with no existing match? Stop. Route it through
componentsfirst. Never write it inline "just this once" — that's exactly the drift this architecture prevents. - Add the page to
flow's navigation map if a prototype nav flow already exists (don't leave new pages orphaned/unreachable). - Verify: view source for any
<style>tag or inlinestyle="..."attribute, and for any<script>beyond the shared includes — both are automatic fails.
Output convention
pages/<page-name>.html ← markup only, references design-system/* in <head>
Checklist
- Zero inline
<style>, zerostyle="..."attributes - Zero page-specific
<script>logic (shared includes only) - Every component used exists in
components.css/foundation library — none invented ad hoc - Hero/opening treats the page's specific job as a thesis, not a generic template
- Reachable from the prototype's
flownavigation, if one exists
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 · 46 lines · 0 tokens per session scan A 8a27874ec89c
page is a command published in the GitHub repository alwkala/tidyfactor-design (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 520 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-31.
Other commands, from other repositories
github-issue
Create a GitHub issue from a natural language description.
test
Hello world test command.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
critique-ux
Run a focused UX critique on a screen — affordances, information density, and hierarchy — and output a prioritised fix list.
design-onboarding
Design a first-run experience end to end — activation path, progressive disclosure, and time to first value.
frame-problem
Structure an ambiguous design challenge into a clear problem definition with constraints and criteria.