agentmods.dev

YSMParser AGENTS.md

Development instructions for YSMParser, a C++20 project that reads and exports .ysm files. It explains the native command-line and browser or Node.js WebAssembly versions, project layout, and parser entry points.

In plain words
What is it for?
Use it when changing .ysm parsing, adding version-specific parser behavior, updating the command-line tool, or modifying the WebAssembly browser interface.
Why use it?
It helps contributors understand where parsing logic and web files belong, and how the different runtime versions share the same core.

Instructions file for CodexOpenCode

572 3mo ago A scan 1,345 tokens original MIT
View the source file OpenYSM/YSMParser
Install

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.

agentmods
npx agentmods add instructions/openysm/ysmparser/agents-md
Clone the repo
git clone --depth 1 https://github.com/OpenYSM/YSMParser

Made for: Codex, OpenCode.

Per session 1,345 This file is loaded in full into every session.
When invoked 1,345 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01345 $0.01345
Opus 5 $0.00673 $0.00673
Sonnet 5 $0.00269 $0.00269
Haiku 4.5 $0.00135 $0.00135

Measured 2d ago against content hash 590c822739c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

YSMParser AGENTS.md 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.

AGENTS.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

Repository expectations

  • Use CRLF (preferred windows visual studio)

Project overview

  • This repository is a C++20/CMake project for parsing and exporting .ysm files.
  • There are two supported runtime paths:
    • Native CLI tool: batch-processes .ysm files from an input directory to an output directory.
    • WebAssembly build: compiles the same parser core for browser or Node.js use via Emscripten.
  • Main project code lives in YSMParser/.
  • Browser UI assets live in web/.
  • Third-party dependencies are vendored under external/.

Key entry points

  • Native CLI entry: YSMParser/main.cpp
  • Parser abstraction and factory:
    • YSMParser/parsers/YSMParser.hpp
    • YSMParser/parsers/YSMParser.cpp
  • Version-specific parsers:
    • YSMParser/parsers/YSMParserV1.cpp
    • YSMParser/parsers/YSMParserV2.cpp
    • YSMParser/parsers/v3/YSMParserV3.cpp
  • V3 header/path mapping helpers:
    • YSMParser/parsers/v3/YSGPHeaderParser.hpp
    • YSMParser/parsers/v3/PlayerTextureCollector.hpp
  • Web UI:
    • web/index.html
    • web/app.js

Current parser architecture

  • YSMParserFactory::Create() reads the input file and selects a parser implementation by header/version.
  • V1 parser:
    • Uses AES-CBC + zlib.
    • Exports resources directly from an in-memory map.
  • V2 parser:
    • Similar to V1, filename is base64-encoded, but derives the real AES key using MD5 + Java-style PRNG before decrypting payloads.
  • V3 parser is the main complexity center:
    • Parses YSGP header metadata.
    • Verifies file integrity with CityHash.
    • Decrypts with custom XChaCha20-based logic plus MT19937 XOR.
    • Decompresses with zstd.
    • Deserializes models, animations, textures, sounds, language files, controllers, and metadata JSON.
    • Exports files using header-derived hashed path mappings when available.

CLI behavior

  • CLI app name in code: YSM File Decryptor.
  • Important arguments:
    • -i, --input: input directory, required.
    • -o, --output: output directory, required.
    • -v, --verbose: detailed per-file logging.
    • -j, --threads: parallel file processing, 0 means auto.
  • The CLI scans recursively for .ysm files only.
  • Each input file is exported into its own subdirectory under the output root, usually named after the input stem.
  • In non-verbose mode, stdout is intentionally silenced during parsing and a progress renderer is shown instead.
  • Verbose mode forces single-threaded execution to keep logs ordered.
  • If output-directory name collisions are detected between files, the tool also forces single-threaded execution.

Read the full file on GitHub · 122 lines

Changes

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.

  1. 2d ago First seen · 122 lines · 1,345 tokens per session scan A 590c822739c9

Subscribe to this mod's changes

YSMParser AGENTS.md is an instructions file published in the GitHub repository OpenYSM/YSMParser (572 stars, last pushed 3mo ago), licensed MIT. It adds 1,345 tokens to every session, about $0.0067 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.

Browser automationLanguagesPlanning
Related

Other instructions, from other repositories

Browser4 CLAUDE.md

Instructions for platonai/Browser4, covering browser4 — project context for claude, architecture, key dispatch chain (cli → browser), batch commands and e2e test structure.

platonai/Browser4 · 1,205 tokens

spring-ai-agentcore AGENTS.md

Instructions for spring-ai-community/spring-ai-agentcore, covering agents.md, project overview, architecture, key components and artifact store classes.

spring-ai-community/spring-ai-agentcore · 1,370 tokens

flyto-core CLAUDE.md

Instructions for flytohub/flyto-core, covering claude notes, cross-agent handoff and shared code intelligence.

flytohub/flyto-core · 367 tokens

deckforge AGENTS.md

Instructions for tph-kds/deckforge, covering deckforge agent entry point, code intelligence, read order, default routing and non-negotiable implementation rules.

tph-kds/deckforge · 498 tokens

fast-browser CLAUDE.md

Claude Code instructions for m4ttstack/fast-browser, covering fast browser plugin, where a change belongs, fork branch: use fast-browser-runtime, releasing a new runtime and re-pinning this repo: use the script.

m4ttstack/fast-browser · 1,446 tokens

agentoscope AGENTS.md

Instructions for rafaelcg/agentoscope, covering agentoscope — agent instructions, what this is, layout, commands and conventions.

rafaelcg/agentoscope · 664 tokens