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/dynamods/dynamohome/reactnpx skills add DynamoDS/DynamoHome --skill reactgit clone --depth 1 https://github.com/DynamoDS/DynamoHomeWhat 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.00000 | $0.00599 |
| Opus 5 | $0.00000 | $0.00300 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Skills – DynamoHome
Component rules
Always use functional components:
// ✅
export const MyComponent = ({ title }: MyComponentProps) => <div>{title}</div>;
// ❌ Never
export class MyComponent extends React.Component { ... }
Define explicit prop interfaces:
// ✅
interface GraphGridItemProps {
name: string;
path: string;
onOpen: (path: string) => void;
}
export const GraphGridItem = ({ name, path, onOpen }: GraphGridItemProps) => { ... };
// ❌
export const GraphGridItem = ({ name, path, onOpen }: any) => { ... };
CSS Modules — mandatory:
import styles from './GraphGridItem.module.css';
// Access with bracket notation
<div className={styles['graph-item']}>
// ❌ Never global class names or inline styles
<div className="graph-item">
<div style={{ color: 'red' }}>
State management
- Component-level state:
useState - Shared user preferences:
useSettings()hook (wrapsSettingsContext) - No external state libraries — Context API only
import { useSettings } from '../SettingsContext';
const { recentPageViewMode, setRecentPageViewMode } = useSettings();
Hooks
- Use built-in hooks:
useState,useEffect,useCallback,useMemo,useRef,useContext - Consume context via
useSettings()— do not useuseContext(SettingsContext)directly - Use
useIntl()from react-intl when you need a string value (not JSX)
Approved libraries — do not add others
| Library | Usage |
|---|---|
| react-intl | <FormattedMessage>, useIntl() |
| react-table | useTable() hook in GraphTable and SamplesTable |
| react-split-pane | <SplitPane> in LayoutContainer |
Folder placement
| Component type | Location |
|---|---|
| Used by one module | src/components/[Module]/ |
| Used by 2+ modules | src/components/Common/ |
| App-level | src/components/ (LayoutContainer, MainContent, SettingsContext) |
What NOT to do
- Do not add Redux, Zustand, Recoil, MobX, Jotai, or any state management library
- Do not add component libraries (Material UI, Ant Design, Chakra, shadcn, etc.)
- Do not use
React.FCtype — prefer explicit prop interfaces with arrow function components - Do not use
React.memo,React.lazy, orSuspenseunless explicitly requested - Do not use
anyfor prop types, state, or return types in new code
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.
- yesterday First seen · 78 lines · 0 tokens per session scan A 0dd2c6569db5
react is a skill published in the GitHub repository DynamoDS/DynamoHome (2 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 599 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…