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/ivanwng97/pixtuoid/add-sourcenpx skills add IvanWng97/pixtuoid --skill add-sourcegit clone --depth 1 https://github.com/IvanWng97/pixtuoidWrote 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/ivanwng97/pixtuoid/add-source)<a href="https://agentmods.dev/skills/ivanwng97/pixtuoid/add-source"><img src="https://agentmods.dev/badge/skills/ivanwng97/pixtuoid/add-source.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.00120 | $0.01366 |
| Opus 5 | $0.00060 | $0.00683 |
| Sonnet 5 | $0.00024 | $0.00273 |
| Haiku 4.5 | $0.00012 | $0.00137 |
Grade A, and why
add-source 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 5d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
add-source (v1)
Adding an agent CLI is not a single-file change — it spans pixtuoid-core
(decoder + registry + tests), the pixtuoid binary (runtime wiring + install
target + badge hue), and the site manifest. Several steps have test teeth
that only just preflight's FULL run catches, not the targeted source/install
suites — so an agent that stops at "it compiles" ships a red PR.
When to use
- "Add support for " / "integrate " / "add a source for X".
- A new transcript-bearing OR hook-only coding CLI should show up as sprites.
The authoritative checklist
The complete, current step list lives in crates/pixtuoid-core/CLAUDE.md
("multi-source decoding" / "Adding a new agent CLI") — read it first; it is the
source of truth and stays current. The Copilot-format summary is
.github/prompts/add-source.prompt.md.
Before you start, decide transcript-bearing vs hook-only (invariant #3): a
hook-only CLI (Reasonix/CodeWhale/opencode/Cursor) sets transcript: None, skips
the runtime wiring + Source impl, and ships a hook.custom decoder + an
install/ target instead.
The test-teeth steps agents miss
These are the ones with a failing test attached — do NOT stop before them:
site/src/sources.jsonrow — a manifest bridge test fails until it exists; thenjust gen-readmeto sync the README.- Per-source badge hue — a
Theme::source(SourceColors) field in EVERY theme file + adashboard_linematch arm; two guard tests fail otherwise. pub fn <cli>_home()if the CLI has a custom config root — one fn honoring its*_HOMEprecedence, called from BOTH the watcher'sdefault_paths()AND the installer'sdefault_config_path()so they can't disagree. Audit that precedence against the CLI's OWN resolver per axis first (#880; axis list inCONTRIBUTING.mdstep- — guessed rather than read, it is fail-silent.
- A captured fixture under
tests/sources/fixtures/<name>/<scenario>/exercising the SessionStart hook — the conformance test forces one, and its one-AgentId assertion guards against the reason-field ghost. sources --jsonCLI golden —crates/pixtuoid/tests/snapshots/cli/sources.json, the real-binary end-to-end golden the Raycast--jsoncontract rides. The new source's row must appear orcli_json::sources_json_lists_every_source_in_an_isolated_homereds; regenerate withSNAPSHOTS=overwrite cargo test -p pixtuoid --test cli_json.wire_to_pixelsmatrix row —crates/pixtuoid/tests/wire_to_pixels.rs: add aWireCase(reuse your SessionStart fixture; a hook-only source usesDecodeKind::Hook+Transport::Hook, like cursor/hermes — a transcript source the JSONL variant) AND the per-source<name>_..._renders_a_painted_spritetest, orwire_matrix_covers_every_registered_sourcereds ("registration is not coverage").
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.
- 5d ago First seen · 86 lines · 120 tokens per session scan A 8cf12ba419e6
add-source is a skill published in the GitHub repository IvanWng97/pixtuoid (467 stars, last pushed yesterday), licensed MIT. It adds 120 tokens to every session and 1,366 once invoked, about $0.0006 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
ast-grep
Use for ast-grep project setup, rule authoring, rule debugging, and structural search workflows.
generate2dmap
Generate and revise production-oriented 2D game maps with built-in image generation as the default visual asset source, choosing a visual model, runtime object model, collision model, art direction, and engine/export target. Use when Codex needs to create or integrate RPG maps, monster-taming maps, tactical arenas…
generate2dsprite
Generate and postprocess general 2D game assets and animation sheets: pixel-art sprites, clean HD map props, creatures, characters, NPCs, spells, projectiles, impacts, props, summons, and transparent GIF exports. Use when Codex should infer the asset plan from a natural-language request, match a reference or map art…
skill-installer
Install VT Code skills into /.agents/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo, including private repos.
video2dsprite
Grok Build ONLY. Turn a 2D character still into smooth animation sprites via imagegen/imageedit base → imagetovideo (6s/10s run-in-place) → ffmpeg frames → magenta chroma-key → dense sampled sprites (strip/grid/GIF). Use when the user wants video-to-sprite, motion capture from generated video, smoother run/walk cycles…
migrate-agent-plugin
Migrate an existing Claude, Copilot, Codex, Cursor, Kiro, VS Code, or other client-specific agent plugin to the portable Agent Plugins v1 structure while preserving platform-specific hooks, agents, commands, LSP, UI, and marketplace behavior. Use when auditing, converting, or modernizing an agent plugin.