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/zerodeng01/sublinkpro/theme-checknpx skills add ZeroDeng01/sublinkPro --skill theme-checkgit clone --depth 1 https://github.com/ZeroDeng01/sublinkProWhat 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.00035 | $0.01323 |
| Opus 5 | $0.00017 | $0.00661 |
| Sonnet 5 | $0.00007 | $0.00265 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
theme-check 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 3d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Theme Check Skill
Comprehensive checklist for frontend theme adaptation changes.
When to use this skill
Use this skill when:
- Modifying colors, surfaces, shadows, borders, icons, dialogs, panels, preview cards, overlays, notices, chips, rich text, or status colors
- Changing theme infrastructure (
webs/src/themes/*,webs/src/utils/colorUtils.js) - Updating shared
sxhelpers or common dialog/card/panel styles - Working on any UI component that affects light/dark mode presentation
Prerequisites
Before running this checklist:
- Read
docs/frontend-theme-guidelines.mdfor complete theme rules - Identify the blast radius: page, module, shared component, or theme infrastructure
- Find reference patterns in the codebase (NodePreview*, Chain*, Airport* clusters)
Checklist
1. Mode Coverage
- Checked both light and dark modes (not just visual validation in current mode)
- Verified with actual theme toggle, not just screenshots
2. Device Coverage
- Checked desktop view
- Checked mobile view
- Verified responsive breakpoints (
useMediaQuery) - Tested fullscreen dialogs on mobile
- Checked safe-area handling
3. Component Structure Coverage
- Page body
- Dialogs (
Dialogcomponent) - Drawers (
Drawercomponent) - Popovers (
Popovercomponent) - Menus (
Menucomponent) - Tooltips (
Tooltipcomponent) - Preview cards
- Detail panels
- Footer overlays
- Empty states
- Skeletons
- Notification/overlay entry points
4. Text Hierarchy
- Primary text (
text.primary) - Secondary text (
text.secondary) - Icons
- Chips
- Badges
- Links
- Code blocks (
code,pre) - Placeholders
- Helper text
- Disabled copy
- State colors (success/warning/error/info)
5. Interactive States
- Default state
- Hover state
- Active/selected state
- Disabled state
- Focus-visible state
- Expanded/collapsed state
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.
- 3d ago First seen · 159 lines · 35 tokens per session scan A a551c8ec09d5
theme-check is a skill published in the GitHub repository ZeroDeng01/sublinkPro (1,605 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,323 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
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.…