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/vitestnpx skills add ggombee/code-forge --skill vitestgit 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.00028 | $0.02018 |
| Opus 5 | $0.00014 | $0.01009 |
| Sonnet 5 | $0.00006 | $0.00404 |
| Haiku 4.5 | $0.00003 | $0.00202 |
Grade A, and why
vitest 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vitest 컨벤션
vitest.config.ts 설정
// vitest.config.ts
import { defineConfig } from 'vitest/config';
import react from '@vitejs/plugin-react';
import path from 'path';
export default defineConfig({
plugins: [react()],
test: {
globals: true, // describe, it, expect를 전역으로 사용
environment: 'jsdom', // 브라우저 환경 시뮬레이션
setupFiles: ['./src/test/setup.ts'],
coverage: {
provider: 'v8',
reporter: ['text', 'html', 'lcov'],
exclude: [
'node_modules/**',
'src/test/**',
'**/*.config.ts',
'**/*.d.ts',
],
},
},
resolve: {
alias: {
'@': path.resolve(__dirname, './src'),
},
},
});
// src/test/setup.ts
import '@testing-library/jest-dom';
// 전역 mock 설정 등
파일 구조
src/
├── utils/
│ ├── formatPrice.ts
│ └── __tests__/
│ └── formatPrice.test.ts
├── hooks/
│ ├── useOrderStatus.ts
│ └── __tests__/
│ └── useOrderStatus.test.ts
└── components/
├── OrderCard.tsx
└── __tests__/
└── OrderCard.test.tsx
기본 테스트 구조
// utils/__tests__/formatPrice.test.ts
import { describe, it, expect, beforeAll, afterAll } from 'vitest';
import { formatPrice, formatPriceWithUnit } from '../formatPrice';
describe('formatPrice', () => {
describe('정상 케이스', () => {
it('양수 금액을 천 단위 쉼표로 포맷', () => {
expect(formatPrice(10000)).toBe('10,000');
});
it('소수점 금액 처리', () => {
expect(formatPrice(9999.99)).toBe('9,999.99');
});
});
describe('경계값', () => {
it('0원 처리', () => {
expect(formatPrice(0)).toBe('0');
});
it('1원 처리', () => {
expect(formatPrice(1)).toBe('1');
});
});
describe('에러 케이스', () => {
it('음수 처리', () => {
expect(() => formatPrice(-1000)).toThrow();
});
it('NaN 처리', () => {
expect(formatPrice(NaN)).toBe('0');
});
});
});
vi.* API
vi.fn() - Mock 함수
import { vi, describe, it, expect } from 'vitest';
describe('useOrderActions', () => {
it('주문 삭제 시 onSuccess 콜백 호출', async () => {
const onSuccess = vi.fn();
const onError = vi.fn();
await deleteOrder('order-1', { onSuccess, onError });
expect(onSuccess).toHaveBeenCalledOnce();
expect(onSuccess).toHaveBeenCalledWith({ id: 'order-1' });
expect(onError).not.toHaveBeenCalled();
});
});
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 · 326 lines · 28 tokens per session scan A dfc9b16603cc
vitest is a skill published in the GitHub repository ggombee/code-forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 2,018 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…