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/gh-actionnpx skills add live-codes/livecodes --skill gh-actiongit 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.00037 | $0.01741 |
| Opus 5 | $0.00018 | $0.00870 |
| Sonnet 5 | $0.00007 | $0.00348 |
| Haiku 4.5 | $0.00004 | $0.00174 |
Grade A, and why
livecodes/gh-action 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LiveCodes — GitHub Action: Preview in LiveCodes
The Preview in LiveCodes GitHub Action generates preview links to LiveCodes playgrounds for code changes in pull requests and posts them as PR comments.
Use case: Library authors can preview changes in the playground before merging PRs.
How It Works
- PR is created or updated
- Action optionally installs dependencies and builds the project
- Action scans
.livecodes/folder for playground configurations - Generates playground URLs with your new code
- Posts comment with preview links to the PR
Setup
Two Required Workflow Files
The action requires two workflow files that must be merged to the default branch first.
1. Trigger workflow .github/workflows/livecodes-preview.yml:
name: livecodes
on: [pull_request]
jobs:
build_and_prepare:
runs-on: ubuntu-latest
name: Generate Playgrounds
steps:
- name: Checkout
uses: actions/checkout@v3
- name: Build and generate
uses: live-codes/preview-in-livecodes@v1
with:
# Optional: install-command: "npm install"
# Optional: build-command: "npm run build"
# Optional: base-url: "https://{{LC::REF}}.my-project.pages.dev"
2. Comment workflow .github/workflows/livecodes-post-comment.yml:
name: comment
on:
workflow_run:
workflows: ['livecodes']
types:
- completed
jobs:
upload:
runs-on: ubuntu-latest
permissions:
pull-requests: write
if: >
github.event.workflow_run.event == 'pull_request' &&
github.event.workflow_run.conclusion == 'success'
steps:
- uses: live-codes/pr-comment-from-artifact@v1
with:
GITHUB_TOKEN: ${{ github.token }}
Two separate workflows are needed because each runs in a different security context. See GitHub security article for details.
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 · 269 lines · 37 tokens per session scan A 30ff47171ddd
livecodes/gh-action is a skill published in the GitHub repository live-codes/livecodes (1,488 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 1,741 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
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.