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 hamzaPixl/pixl-ai --skill websitegit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/hamzapixl/pixl-ai/website)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/website"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/website/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/hamzapixl/pixl-ai/website"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/website.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.00086 | $0.04203 |
| Opus 5.5 | $0.00034 | $0.01681 |
| Sonnet 5.5 | $0.00017 | $0.00841 |
| Haiku 4.5 | $0.00009 | $0.00420 |
Grade A, and why
website 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.
How it starts
The opening of the file, as written. The whole thing — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup
Read config.json in this skill directory (if it exists):
framework— frontend framework; default "nextjs"styling— styling approach; default "tailwind"component_library— UI component library; default "shadcn-ui"package_manager— package manager; default "bun"
These defaults apply to Mode A (Discovery). Mode B/C override from the design-spec.json. If config.json is absent and the project already has a framework installed, detect it from package.json instead.
Overview
End-to-end website creation using Next.js with shadcn/ui and Tailwind CSS. Three operating modes:
| Mode | Input | Skips | Use Case |
|---|---|---|---|
| A: Discovery | Description or brief | Nothing | New site from scratch |
| B: Spec-fed | design-spec.json |
Steps 1-2 (discovery + design) | New site from extracted design |
| C: Replicate | design-spec.json from URL |
Steps 1-3 (discovery + design + content) | Exact reproduction of existing site |
Mode Detection
- If input is a path to
design-spec.json→ checkmeta.source_type:"url"→ default to Mode C (replicate), confirm with user"figma"or"screenshot"→ Mode B (spec-fed)"discovery"→ Mode A (should not happen, but treat as A)
- If input is a Figma URL or website URL → run
/design-extractionfirst, then re-enter with the resulting spec - If input is a text description → Mode A (discovery)
Mode A: Full Discovery Pipeline
Runs all 8 steps below (Steps 1 through 8).
Mode B: Spec-Fed
- Read the
design-spec.json - Skip Steps 1-2 (discovery and design) — the spec IS the design system
- Run Step 3 (Content) — generate content based on spec's
metaandpagesstructure - Continue with Steps 4-8 (scaffold → build → components → blog → polish)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 318 lines · 86 tokens per session scan A 979eae531da4
website is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 86 tokens to every session and 4,203 once invoked, about $0.0003 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-03.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
material-ui-tailwind
Integrates Material UI with Tailwind CSS v4 using cascade layers (enableCssLayer, @layer order) and documents Tailwind v3 interoperability (preflight, important, injectFirst, portals). Use when combining MUI with Tailwind utilities, slotProps className, or theme token bridges.
fuzzy-ranking
Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…