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/nschneir/project64/6502-assemblynpx skills add nschneir/Project64 --skill 6502-assemblygit clone --depth 1 https://github.com/nschneir/Project64Wrote 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/nschneir/project64/6502-assembly)<a href="https://agentmods.dev/skills/nschneir/project64/6502-assembly"><img src="https://agentmods.dev/badge/skills/nschneir/project64/6502-assembly.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.1 | $0.00058 | $0.04768 |
| Opus 5 | $0.00029 | $0.02384 |
| Sonnet 5 | $0.00012 | $0.00954 |
| Haiku 4.5 | $0.00006 | $0.00477 |
Grade A, and why
6502-assembly 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 6d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 6d ago First seen · 321 lines · 58 tokens per session scan A 0da3693b9231
6502-assembly is a skill published in the GitHub repository nschneir/Project64 (2 stars, last pushed 13d ago), with no licence file. It adds 58 tokens to every session and 4,768 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-31.
Other skills, from other repositories
6502-assembly
Use when writing or debugging 6502 assembly for the Commodore PET with ca65/ld65 via pet build or pet run. Covers the PET program skeleton, the BASIC SYS stub, calling ROM routines, and 6502 gotchas.
ue-mcp-native-cpp
Use when writing or modifying native C++ UCLASSes in an Unreal project via ue-mcp. Covers createcppclass → writecppfile → livecodingcompile loop, when to use build vs Live Coding, and the addmoduledependency workflow. Pulls in any time the user asks to write a new native class, add a UPROPERTY, or implement a…
pet-development
Use when developing, running, or debugging Commodore PET software (Commodore BASIC or 6502 assembly) on the VICE emulator with the pet CLI or the pet-tools MCP server. Covers the build/run/observe/debug loop, the stopped-state discipline, PET text encodings, and per-model differences.
6502-debugging
Use when a PET program misbehaves at runtime — crashes, corruption, wrong values, dead input, visual glitches — and you need a procedure, not a guess. Symptom-indexed playbook of runtime debugging procedures using pet-tools.
cross-platform-demo
Run the shortest visible demo path across VICE and C64U.
graphics-demo
Execute PETSCII, sprite, bitmap, and frame-capture graphics workflows.