SkillHub is a self-hosted registry where organizations publish, discover, version, and manage reusable skills for AI agents. Teams use it to share governed skill packages privately, with namespaces, role-based access control, audit logs, and CLI installation; the catalogue entries are skills and related agent integrations that can be managed through it.
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/iflytek/skillhub/frontend-conventionsnpx skills add iflytek/skillhub --skill frontend-conventionsgit clone --depth 1 https://github.com/iflytek/skillhubWrote 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/iflytek/skillhub/frontend-conventions)<a href="https://agentmods.dev/skills/iflytek/skillhub/frontend-conventions"><img src="https://agentmods.dev/badge/skills/iflytek/skillhub/frontend-conventions.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.00036 | $0.01040 |
| Opus 5 | $0.00018 | $0.00520 |
| Sonnet 5 | $0.00007 | $0.00208 |
| Haiku 4.5 | $0.00004 | $0.00104 |
Grade A, and why
frontend-conventions 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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Conventions Skill
Trigger
Use this skill when:
- Adding or modifying React/TypeScript frontend code
- Creating new pages, features, entities, or shared components
- Changing API client calls or data fetching patterns
Rules
Feature-Sliced Design
Place code at the lowest appropriate layer:
| Layer | Path | Purpose |
|---|---|---|
| Pages | web/src/pages/ |
Route-level page components |
| Features | web/src/features/ |
Business features (search, upload, review, etc.) |
| Entities | web/src/entities/ |
Domain entity display logic (skill, user, namespace) |
| Shared | web/src/shared/ |
Reusable UI components, hooks, utilities |
Current features:
admin— Admin panel (user management, labels, search)auth— Login, OAuth flows, device authgovernance— Skill governance actions (hide, yank, archive)namespace— Namespace management (members, settings)notification— User notifications and inboxpromotion— Skill promotion between scopespublish— Skill upload/publish UIreport— Skill reportingreview— Review workflow UIsearch— Skill search and filteringsecurity-audit— Security audit viewerskill— Skill detail, listing, cardssocial— Stars, ratings, subscriptionstoken— API token management
Data Fetching
- Always use TanStack Query (
@tanstack/react-query) for server state. - Never use
useEffectfor data fetching. - Use
openapi-fetchclient with generated types fromweb/src/api/generated/schema.d.ts. - Never use
anytypes.
State Management
- TanStack Query for server state (API data, caching, invalidation, optimistic updates)
- Zustand for local/UI state (theme, sidebar, modals, form state)
Component Composition
- Radix UI primitives:
@radix-ui/react-dropdown-menu,@radix-ui/react-select - class-variance-authority (cva) for component variants
- clsx + tailwind-merge for class merging
cn()utility:web/src/shared/lib/utils.ts- shadcn/ui is NOT used as a library
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.
- 5d ago First seen · 125 lines · 36 tokens per session scan A 67613120a75f
frontend-conventions is a skill published in the GitHub repository iflytek/skillhub (4,968 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 1,040 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
aicoin-onchain
Use this skill for on-chain DEX trading and wallet operations on EVM/Solana chains: token swap quotes, swap execution, wallet portfolio/balance queries, gas estimation, transaction broadcasting, token search/info on Ethereum/Solana/Base/BSC/Arbitrum/Polygon etc. Use when user says: 'swap ETH for USDC', 'buy token…
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openclaw-docs
Find authoritative guidance for installing, configuring, operating, securing, and troubleshooting OpenClaw, including channels, model providers, Gateway operations, tools, plugins, automation, nodes, multi-agent routing, and CLI errors. Use for any question or maintenance task involving an OpenClaw installation…
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.