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/jonnyton/tinyassets/website-editingnpx skills add Jonnyton/TinyAssets --skill website-editinggit clone --depth 1 https://github.com/Jonnyton/TinyAssetsWhat 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.00073 | $0.03717 |
| Opus 5 | $0.00036 | $0.01858 |
| Sonnet 5 | $0.00015 | $0.00743 |
| Haiku 4.5 | $0.00007 | $0.00372 |
Grade C, and why
website-editing scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
7. **For HMR-sensitive Svelte changes** (vite config, `+layout.ts`, prerender entries): rebuild from scratch (`rm -rf build` first) — stale `.svelte-kit/` artifacts can mask real failures. How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Website editing
WebSite/site-react/ is the current React/Next production source for
tinyassets.io; it deploys manually through deploy-site-react.yml.
WebSite/site/ is the retained Svelte rollback source and deploys only through
an explicit dispatch of deploy-site.yml. These are project-level website
rules — they apply equally to every provider (Codex, Cursor, Aider, Claude Code,
), but the detailed rules live here so AGENTS.md can stay lean. When in
doubt, add website conventions to this skill and keep provider-specific files
as pointers or harness notes.
Before you edit anything
- Read
WebSite/PREVIEW.md— the canonical two-tree preview loop. - Edit and build React first. Preview
WebSite/site-react/athttp://localhost:3000/; useWebSite/site-react/PREVIEW.mdfor the production-exact and hosted paths. - Preserve Svelte rollback parity. Mirror the intended user-visible behavior into
WebSite/site/and preview it at the hard-pinnedhttp://localhost:5173/throughWebSite/preview.bat. - Read
WebSite/DEPLOY.mdif you might ship — it covers the normal review/merge path, manual React deployment, dispatch-only Svelte rollback, and live verification.
The iteration loop
Once the React dev server is up and Jonathan has the tab open at
localhost:3000/:
Jonathan: "the hero subline is too long"
Agent: [edits the React production component, then mirrors Svelte parity]
Jonathan: [tab updates by itself] ← HMR, no F5 needed
Jonathan: "yeah that's better"
You do not rebuild or redeploy to show a development change. The React dev server pushes updates to tabs on port 3000; Vite pushes Svelte rollback updates to tabs on port 5173. Each tree has its own preview. Review React first, then the Svelte parity result.
If F5 is ever needed, that's a signal HMR misfired — investigate, don't normalize the workaround. The intended state is "edit a file, tab updates, no input from the user."
Transparent capture — when a page intentionally publishes a real chatbot conversation
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.
- 2d ago First seen · 153 lines · 73 tokens per session scan C 9eb13b61a51d
website-editing is a skill published in the GitHub repository Jonnyton/TinyAssets (1 stars, last pushed 2d ago), licensed MIT. It adds 73 tokens to every session and 3,717 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
design-guide
Paperclip UI design system guide for building consistent, reusable frontend components. Use when creating new UI components, modifying existing ones, adding pages or features to the frontend, styling UI elements, or when you need to understand the design language and conventions. Covers: component creation, design…
Shade ShadCN install
Guardrails for running pnpm dlx shadcn@latest add in Shade — never overwrite existing components, fresh branch first, swap raw colours for semantic tokens after integrating. Trigger when the user proposes a shadcn add, or when a fresh ShadCN-shaped file lands in apps/shade/src/components/ui.
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.
author-component
Create or review Blazor components (.razor files) with correct architecture. USE FOR: writing new Blazor components that do NOT involve JavaScript interop, implementing parameters and EventCallback, RenderFragment slots, component lifecycle (OnInitializedAsync, OnParametersSet), async patterns, IAsyncDisposable…
obsidian-layout-adjustment
Workflow for working with the user on changing how Obsidian looks using CSS snippets. Use this whenever the user asks to restyle Obsidian, tune a vault's visual layout, adjust tabs, sidebars, note surfaces, properties, backlinks, graph panes, file explorer rows, icons, links, shadows, active states, or CSS snippets.…