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/cvander/maya/eighty_sixnpx skills add cvander/Maya --skill eighty_sixgit clone --depth 1 https://github.com/cvander/MayaWhat 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.00014 | $0.00574 |
| Opus 5 | $0.00007 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
eighty-six 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.
What it actually says
Eighty-Six
Manage the 86 list of currently unavailable items. Add items when they run out, remove them when restocked, and list what is currently unavailable.
Idempotent. Writes only to data/86/current.md. No PII in output.
When to Use
- When a bartender reports an item is out (86 it)
- When a delivery arrives and restocks an item (un-86 it)
- Before service to check what is currently unavailable
- When a guest asks about availability
Procedure
Run the skill from the repo root:
# List currently 86'd items (default behavior)
python -m skills.eighty_six --format json
# Explicitly list
python -m skills.eighty_six --list --format json
# Add an item to the 86 list
python -m skills.eighty_six --add "Pliny the Elder" --reason "Keg kicked" --reported-by "Alex" --format json
# Remove an item (back in stock)
python -m skills.eighty_six --remove "Pliny the Elder" --format json
Parse the JSON result:
status: "ok" (all clear or action completed) or "warn" (items on 86 list)findings: array with CURRENTLY_86D, ITEM_86D, or ITEM_BACK codesdata.items: list of currently 86'd items (on --list)data.count: number of 86'd items (on --list)
Exit Codes
| Code | Meaning |
|---|---|
| 0 | OK - action completed or no items 86'd |
| 1 | Warn - items currently on the 86 list |
| 2 | Config error (bad arguments) |
| 3 | Data error (can't read/write data file) |
| 10 | Unexpected error |
Verification
After running, confirm:
- Exit code is 0 or 1 (not 2, 3, or 10)
- stdout is valid JSON (when using --format json)
- For --add: item appears in subsequent --list
- For --remove: item no longer appears in --list
What ships with it
10 files 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.
- __init__.py 0 B runs code
- __main__.py 644 B runs code
- fixtures/FIXTURES.md 207 B
- fixtures/happy_path/current.md 143 B
- fixtures/happy_path/expected.json 170 B
- fixtures/warn_case/current.md 292 B
- fixtures/warn_case/expected.json 960 B
- main.py 10 KB runs code
- manifest.toml 301 B
- test_main.py 10.0 KB runs code
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 · 73 lines · 14 tokens per session scan A 12c552a5ccd6
eighty-six is a skill published in the GitHub repository cvander/Maya (10 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 574 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.