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 VersoXBT/claude-initial-setup --skill hooks-masterygit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWrote 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/versoxbt/claude-initial-setup/hooks-mastery)<a href="https://agentmods.dev/skills/versoxbt/claude-initial-setup/hooks-mastery"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/hooks-mastery/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/versoxbt/claude-initial-setup/hooks-mastery"><img src="https://agentmods.dev/badge/skills/versoxbt/claude-initial-setup/hooks-mastery.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.00079 | $0.01886 |
| Opus 5 | $0.00039 | $0.00943 |
| Sonnet 5 | $0.00016 | $0.00377 |
| Haiku 4.5 | $0.00008 | $0.00189 |
Grade A, and why
hooks-mastery scanned grade A 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(url, { signal: controller.signal }) How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Hooks Mastery
Patterns for writing correct, performant, and composable React hooks.
When to Use
- User is creating custom hooks
- User asks about useCallback, useMemo, or performance optimization
- User has complex state logic that needs useReducer
- User is integrating an external store (Redux, Zustand, vanilla)
- User encounters stale closure bugs or rules of hooks violations
Core Patterns
Custom Hooks -- Extracting Reusable Logic
Custom hooks encapsulate stateful logic for reuse across components. Name them with the use prefix.
import { useState, useEffect, useRef } from 'react'
function useFetch<T>(url: string) {
const [data, setData] = useState<T | null>(null)
const [error, setError] = useState<Error | null>(null)
const [isLoading, setIsLoading] = useState(true)
useEffect(() => {
const controller = new AbortController()
setIsLoading(true)
setError(null)
fetch(url, { signal: controller.signal })
.then((res) => {
if (!res.ok) throw new Error(`HTTP ${res.status}`)
return res.json()
})
.then((json) => setData(json as T))
.catch((err) => {
if (err.name !== 'AbortError') setError(err)
})
.finally(() => setIsLoading(false))
return () => controller.abort()
}, [url])
return { data, error, isLoading }
}
useCallback and useMemo -- When to Memoize
Memoize only when passing callbacks to memoized children or when computation is expensive. Do not memoize everything by default.
import { useCallback, useMemo } from 'react'
function ProductList({ products, onSelect }: Props) {
// Memoize because this is passed to React.memo children
const handleSelect = useCallback(
(id: string) => {
onSelect(id)
},
[onSelect]
)
// Memoize because sorting is O(n log n)
const sorted = useMemo(
() => [...products].sort((a, b) => a.price - b.price),
[products]
)
return (
<ul>
{sorted.map((p) => (
<ProductItem key={p.id} product={p} onSelect={handleSelect} />
))}
</ul>
)
}
const ProductItem = React.memo(({ product, onSelect }: ItemProps) => (
<li onClick={() => onSelect(product.id)}>{product.name}</li>
))
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.
- 8d ago First seen · 247 lines · 79 tokens per session scan A f0ac536d7c18
hooks-mastery is a skill published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 4mo ago), licensed MIT. It adds 79 tokens to every session and 1,886 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
software-frontend
Builds frontend applications across major web stacks. Use when implementing UI, fixing hydration or SSR issues, or setting up modern frontend architecture.
software-localisation
Implements production-grade i18n/l10n for React, Vue, Angular, and Next.js with ICU format and RTL support. Use when setting up or debugging localisation.
theokit-agents
TheoKit agent/LLM integration — agents/.ts convention (AgentBuilder), the tool() builder, capabilities (advanced/DI), useAgent client hook.
dev-nextjs
Next.js development (App Router, Server Components, caching, streaming). Trigger when the user works with Next.js, modifies app/, pages/, next.config, or talks about RSC, Server Actions, Route Handlers, middleware.
theokit-frontend
TheoKit frontend — file-based routing, layouts, theoFetch typed client, useAgent, React patterns.
dev-react-perf
React/Next.js performance optimization. Trigger when the user wants to optimize rendering, reduce re-renders, or improve Core Web Vitals.