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/harkro753/claude-copy/reactnpx skills add HarKro753/claude-copy --skill reactgit clone --depth 1 https://github.com/HarKro753/claude-copyWhat 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.00158 | $0.03187 |
| Opus 5 | $0.00079 | $0.01594 |
| Sonnet 5 | $0.00032 | $0.00637 |
| Haiku 4.5 | $0.00016 | $0.00319 |
Grade A, and why
react 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 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.
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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clone:react — capture session → verified shadcn routes
In: a session folder — pages.json + one folder per page holding ref.png,
source.html, computed.json, meta.json.
Out: a vite + shadcn project at apps/<site>/ui/, one React component per
route in ui/src/routes/, themed from ui/theme.json, where every captured
state's check exits 0 against its own ref.png.
Read references/pipeline.md first — the
CLI, the phases, the loop discipline and the four hard nevers are there and are
not repeated here. This file is only what differs for React.
clone prep <session> --target react
clone extract | resolve | cluster
clone init | map | check | build
Why components, and where the project lives
A screenshot is the resting frame of components that have behaviour. A
command palette cloned as HTML is a div with a fake list; composed from
Command it filters, takes ⌘K, traps focus and returns a value. Hover, focus
rings, disabled states and keyboard nav are all in the component and none of them
are in ref.png. Cloning frames throws that away every time.
The project lives inside the capture folder it clones — apps/<site>/ui/,
one per site, not one for the repo. It costs a node_modules per clone and buys
three things: a tree you can hand to someone whole, a components/ui/ that is
unambiguously this site's to edit, and no path in the loop that leaves the app
folder — the fonts and baked glyphs the route asks for are project assets under
ui/public/, not a sibling directory two levels up.
What prep does differently: states, not duplicate routes
A URL that differs only in its fragment is folded into a state.
new: 1 component, 3 states — base, settings-general, settings-customize-connectors
Under a static target those three captures are three routes, which means
hand-cloning the same shell into three files and fixing every bug three times.
Here they are one component and a state prop, each still gated against its own
ref.png. This is most of what the target buys.
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 · 246 lines · 158 tokens per session scan A 28410f1c654c
react is a skill published in the GitHub repository HarKro753/claude-copy (17 stars, last pushed 1mo ago), licensed MIT. It adds 158 tokens to every session and 3,187 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.