Portable Agent Skill · v0.1.0

Give your agent the right map.

The Sandwich Hime Agent Skill teaches compatible coding agents how to work with .sando without changing pinned versions, hand-editing generated Go, inventing a template-inheritance framework, or blurring the application's HTTP boundary.

License and compatibility: the complete skill folder is offered under 0BSD and supports Hime-san v1.0.0-beta.1 and newer. The compiler and LSP remain AGPL-3.0-only; installing this guidance does not relicense them.

Download and verify the exact archive

Start from the canonical signed Skill release. On Linux, WSL, or another POSIX shell:

curl -fL https://gitea.speelman.ca/attachments/dcc30bab-d4ea-40e6-8f54-fcabc8c7a8ed \
  -o sandwich-hime-skill-v0.1.0.zip
curl -fL https://gitea.speelman.ca/attachments/a42eecec-8b94-4a78-99b6-fb49751b3fad \
  -o sandwich-hime-skill-v0.1.0.zip.sha256
sha256sum -c sandwich-hime-skill-v0.1.0.zip.sha256
unzip -q sandwich-hime-skill-v0.1.0.zip

The expected ZIP SHA-256 is fa1c95bc7f3bad7095776ea04da8215f64dfaf99e80918be3fcd7f0d8cd95677. The archive contains one sandwich-hime directory with five files: SKILL.md, LICENSE, agent metadata, and two concise references.

Put the folder where your agent discovers skills

Codex user scope
Copy sandwich-hime to $CODEX_HOME/skills/sandwich-hime, normally ~/.codex/skills/sandwich-hime.
Open Agent Skills project scope
Copy it to .agents/skills/sandwich-hime in the project that should carry the guidance.
skill_root="${CODEX_HOME:-$HOME/.codex}/skills"
mkdir -p "$skill_root"
cp -R sandwich-hime "$skill_root/sandwich-hime"

Review an existing destination before replacing it. Reload or restart the agent host if it does not discover newly installed folders dynamically.

Useful constraints, not autonomous authority

The skill directs an agent to inspect go.mod, generated provenance, and himesan version --json before choosing commands. It preserves exact dependency versions, installs the runtime first, uses himesan check --json for review, and generates only when writes are authorized.

  • Never hand-edit .sando.go.
  • Treat Trust* values and handwritten components as explicit output capabilities.
  • Keep routing, headers, caching, and deployment in the application.
  • Never run himesan dev for an untrusted repository.
  • Keep .san exclusively for the separate San language.

The folder contains instructions, not an executable. Your agent's own permissions, approvals, sandbox, and human review still control what it may read, write, or run.

Confirm the project before asking for work

himesan version --json
himesan check --json ./...

For the current editor-aware toolchain, the compiler should report v1.0.0-beta.2, runtime ABI sando.v1, and feature lsp-stdio. The project's go.mod remains the authority for its runtime version.