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/language-supportnpx skills add live-codes/livecodes --skill language-supportgit 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.00062 | $0.01604 |
| Opus 5 | $0.00031 | $0.00802 |
| Sonnet 5 | $0.00012 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
livecodes/language-support 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveCodes — Work with Languages
LiveCodes supports 90+ languages across three editors: markup (HTML/templating), style (CSS/preprocessors), and script (JS/compiled languages).
Setup
import { createPlayground } from 'livecodes';
// Basic language setup
createPlayground('#container', {
config: {
markup: { language: 'markdown', content: '# Hello' },
style: { language: 'scss', content: '$color: blue; body { color: $color; }' },
script: { language: 'typescript', content: 'const x: number = 1;' },
},
});
// WASM language (Python)
createPlayground('#container', {
config: {
script: { language: 'python-wasm', content: 'print("Hello from Python")' },
},
});
// Framework template
createPlayground('#container', { template: 'react' });
Core Patterns
Set language for each editor
// Markup languages
markup: { language: 'html', content: '...' } // HTML
markup: { language: 'markdown', content: '...' } // Markdown
markup: { language: 'mdx', content: '...' } // MDX
markup: { language: 'pug', content: '...' } // Pug
markup: { language: 'handlebars', content: '...' } // Handlebars
// Style languages
style: { language: 'css', content: '...' } // CSS
style: { language: 'scss', content: '...' } // SCSS/Sass
style: { language: 'less', content: '...' } // Less
style: { language: 'stylus', content: '...' } // Stylus
// Script languages
script: { language: 'javascript', content: '...' } // JavaScript
script: { language: 'typescript', content: '...' } // TypeScript
script: { language: 'jsx', content: '...' } // JSX
script: { language: 'tsx', content: '...' } // TSX
Use CSS processors
const config = {
style: { language: 'css', content: '...' },
processors: [
'tailwindcss', // Tailwind CSS
'autoprefixer', // Add vendor prefixes
'postcssPresetEnv', // Use future CSS
'cssmodules', // CSS Modules
'cssnano', // Minify
],
};
// Processors run in order listed
// Tailwind should come before PostCSS tools
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 210 lines · 62 tokens per session scan A ae2ae4a06941
livecodes/language-support is a skill published in the GitHub repository live-codes/livecodes (1,488 stars, last pushed 5d ago), licensed MIT. It adds 62 tokens to every session and 1,604 once invoked, about $0.0003 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
prettier-docs
Prettier 3.9.5 — opinionated code formatter. CLI, API, config, plugins, editor integration, CI.
review-pr
Review a Deno runtime pull request for correctness, tests, security, and conventions. Use when asked to review a PR or when a PR number/URL is provided for review.
adev-writing-guide
Comprehensive writing guide for Angular documentation (adev). Covers Google Technical Writing standards, Angular-specific markdown extensions, code blocks, and components. You MUST use this skill any time you plan to create, edit, or review documentation files in adev/ or adev/src/content.
reference-signal-forms
Explains the mental model and architecture of the code under packages/forms/signals. You MUST use this skill any time you plan to work with code in packages/forms/signals.
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
fmt
Format all code in the repository. Run before opening a PR or committing changes.