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/jubscodes/get-shit-pretty/gspdev-runtime-compatnpx skills add jubscodes/get-shit-pretty --skill gspdev-runtime-compatgit clone --depth 1 https://github.com/jubscodes/get-shit-prettyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-runtime-compat)<a href="https://agentmods.dev/skills/jubscodes/get-shit-pretty/gspdev-runtime-compat"><img src="https://agentmods.dev/badge/skills/jubscodes/get-shit-pretty/gspdev-runtime-compat.svg" alt="Measured on agentmods" height="20"></a>What 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.00051 | $0.01902 |
| Opus 5 | $0.00026 | $0.00951 |
| Sonnet 5 | $0.00010 | $0.00380 |
| Haiku 4.5 | $0.00005 | $0.00190 |
Grade A, and why
gspdev-runtime-compat 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 4d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The GSP installer lives at bin/install.js in the repo root. It converts Claude Code's native format into each runtime's expected format. The baseline reference is at ${CLAUDE_SKILL_DIR}/references/baseline.md.
Step 0: Parse request
$ARGUMENTS determines scope:
- A runtime name (
claude,opencode,gemini,codex) — research that runtime only - A concept (
skills,agents,commands,tool-mapping) — compare across all runtimes - A combo (
codex skills,gemini agents) — specific runtime + concept allor empty — full comparison across all runtimes and conceptsdrift— compare docs against current installer and flag mismatches
Step 1: Fetch live documentation
For each runtime in scope, fetch the authoritative docs. Use WebFetch with targeted prompts to extract extension specs.
Claude Code
- Skills:
https://code.claude.com/docs/en/skills - Agents/Subagents:
https://code.claude.com/docs/en/sub-agents - Plugins:
https://code.claude.com/docs/en/plugins - Hooks:
https://code.claude.com/docs/en/hooks
Extract: frontmatter fields, discovery paths, ${CLAUDE_SKILL_DIR}, $ARGUMENTS, context: fork, allowed-tools, disable-model-invocation, user-invocable, agent field, skill precedence rules.
OpenCode
- Skills:
https://opencode.ai/docs/skills/ - Agents:
https://opencode.ai/docs/agents/ - Commands:
https://opencode.ai/docs/commands/ - Rules:
https://opencode.ai/docs/rules/
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.
- 4d ago First seen · 196 lines · 51 tokens per session scan A 17eca8bc5ca7
gspdev-runtime-compat is a skill published in the GitHub repository jubscodes/get-shit-pretty (54 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 1,902 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
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-scan-code-accessibility
Scan generated/authored HTML for accessibility violations with axe-core (Deque) running over JSDOM — structural and semantic rules: ARIA attributes and roles, accessible names, alt text, form labels, heading order, landmarks, semantic HTML, tabindex, duplicate IDs, lang attribute, and 50 more. Use on the CODE side of…
figma-import-tokens
Push design tokens from code INTO Figma as variables — DTCG / tokens.json / a token object → Figma variable collections, modes, and values. Use when the user wants to sync tokens code→Figma: triggers 'import tokens into Figma', 'create Figma variables from my tokens.json / DTCG / Tailwind config', 'sync design tokens…
figma-analyze-component-set
Analyze a Figma COMPONENTSET as a state machine for code generation — extract variant axes (state/size/etc.), map state variants to CSS pseudo-classes (hover→:hover, focus→:focus-visible, disabled→:disabled, error→[aria-invalid]), and compute per-variant visual diffs (only what changes per state). Use when generating…