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/live-codes/livecodes/testingnpx skills add live-codes/livecodes --skill testinggit clone --depth 1 https://github.com/live-codes/livecodesWhat 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.00049 | $0.01831 |
| Opus 5 | $0.00024 | $0.00915 |
| Sonnet 5 | $0.00010 | $0.00366 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
livecodes/testing 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveCodes — Write and Run Tests
LiveCodes includes Jest and Testing Library for automated testing in the browser. Tests run against the result page in real-time.
Setup
import { createPlayground } from 'livecodes';
// Project with tests
createPlayground('#container', {
template: 'jest', // Jest starter template
params: { tests: 'open' }, // Show tests panel
});
// Custom test configuration
createPlayground('#container', {
config: {
activeEditor: 'script',
script: {
language: 'javascript',
content: `
export function add(a, b) {
return a + b;
}
export function greet(name) {
return 'Hello, ' + name;
}
`,
},
tests: {
language: 'javascript',
content: `
import { add, greet } from './script';
describe('add', () => {
test('adds numbers', () => {
expect(add(1, 2)).toBe(3);
});
test('handles negatives', () => {
expect(add(-1, -2)).toBe(-3);
});
});
describe('greet', () => {
test('greets by name', () => {
expect(greet('World')).toBe('Hello, World');
});
});
`,
},
},
params: { tests: 'open' },
});
Core Patterns
Test exports from script editor
// Script editor (script.js)
export default function greet(name) {
return 'Hello, ' + name;
}
export const add = (a, b) => a + b;
// Also available in global scope
window.multiply = (a, b) => a * b;
// Tests editor
import greet, { add } from './script'; // Relative import, no extension
describe('imports', () => {
test('greet', () => {
expect(greet('World')).toBe('Hello, World');
});
test('add', () => {
expect(add(1, 2)).toBe(3);
});
});
describe('globals', () => {
test('multiply', () => {
expect(window.multiply(2, 3)).toBe(6);
});
});
Use Testing Library
// React Testing Library
import { render, screen, fireEvent } from '@testing-library/react';
import '@testing-library/jest-dom';
import userEvent from '@testing-library/user-event';
test('button click', async () => {
render(<MyComponent />);
await userEvent.click(screen.getByText('Click me'));
expect(screen.getByText('Clicked')).toBeInTheDocument();
});
// DOM Testing Library
import { getByText, waitFor } from '@testing-library/dom';
test('element appears', async () => {
document.body.innerHTML = '<div id="root"></div>';
// ... render something
await waitFor(() => {
expect(getByText(document.body, 'Loaded')).toBeTruthy();
});
});
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 · 307 lines · 49 tokens per session scan A 979cdcd3b692
livecodes/testing is a skill published in the GitHub repository live-codes/livecodes (1,488 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 1,831 once invoked, about $0.0002 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
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
photo-sphere-viewer
Use when displaying 360-degree panoramic images (equirectangular/cubemap/dual-fisheye) in web applications, building virtual tours with markers and transitions, embedding interactive panoramas in Vue/React/vanilla JS, or creating 360-degree video players with gyroscope VR support. Photo-Sphere-Viewer v5: JavaScript…
Validate Changes
A workflow to verify that code changes (refactoring, new features) didn't break the scraper or the build.
prettier-docs
Prettier 3.9.5 — opinionated code formatter. CLI, API, config, plugins, editor integration, CI.