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/ggombee/code-forge/jotai-tanstacknpx skills add ggombee/code-forge --skill jotai-tanstackgit clone --depth 1 https://github.com/ggombee/code-forgeWhat 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.00029 | $0.01584 |
| Opus 5 | $0.00015 | $0.00792 |
| Sonnet 5 | $0.00006 | $0.00317 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
jotai-tanstack 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jotai + TanStack Query v5 상태관리
상태 유형별 도구
| 상태 유형 | 도구 | 위치 |
|---|---|---|
| 서버 상태 (API 데이터) | TanStack Query v5 | packages/shared/queries/ |
| 전역 UI/세션 상태 | Jotai | packages/shared/atoms/ |
| 폼 상태 | React Hook Form | 컴포넌트 내부 |
| 로컬 UI 상태 | useState/useReducer | 컴포넌트 내부 |
판단 기준
- 서버에서 온 데이터인가? → React Query
- 여러 컴포넌트가 공유해야 하는 UI 상태인가? → Jotai
- 폼 입력값인가? → React Hook Form
- 이 컴포넌트에서만 쓰는 상태인가? → useState
TanStack Query 구조
디렉토리 구조
packages/shared/
├── queries/
│ └── {도메인}/
│ ├── index.ts # useXxxQuery, useXxxMutation 훅
│ └── queryKeys.ts # 쿼리 키 정의
├── services/
│ └── {도메인}/
│ ├── index.ts # API 호출 함수
│ └── types.ts # 요청/응답 타입
쿼리 키 패턴 (queryKeys 팩토리)
// packages/shared/queries/{도메인}/queryKeys.ts
export const orderKeys = {
all: ['order'] as const,
lists: () => [...orderKeys.all, 'list'] as const,
list: (filters: OrderFilters) => [...orderKeys.lists(), filters] as const,
details: () => [...orderKeys.all, 'detail'] as const,
detail: (id: string) => [...orderKeys.details(), id] as const,
};
쿼리 훅 작성 규칙
// packages/shared/queries/{도메인}/index.ts
import { useQuery, useMutation, useQueryClient } from '@tanstack/react-query';
import { orderKeys } from './queryKeys';
import { orderService } from '@repo/shared/services/order';
export const useOrderQuery = (orderId: string) => {
return useQuery({
queryKey: orderKeys.detail(orderId),
queryFn: () => orderService.getOrder(orderId),
});
};
export const useUpdateOrderMutation = () => {
const queryClient = useQueryClient();
return useMutation({
mutationFn: orderService.updateOrder,
onSuccess: (_, variables) => {
queryClient.invalidateQueries({
queryKey: orderKeys.detail(variables.orderId),
});
},
});
};
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 · 225 lines · 29 tokens per session scan A 903237748efc
jotai-tanstack is a skill published in the GitHub repository ggombee/code-forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 1,584 once invoked, about $0.0001 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.
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…