mcpField
M
mofa-travel-safety

mofa-travel-safety

github.com/nomadamasOther8.2k3.5k installsUpdated 2d ago
Repository

About mofa-travel-safety

mofa-travel-safety is a coding-agent skill for travel-related tasks. It provides runtime-specific instructions and sets boundaries around sensitive actions, credentials, and legal or identity checks.

Key features

  1. 01Runtime-specific instructions
  2. 02Bundled helper-file listing
  3. 03Explicit approval for sensitive actions
  4. 04Credential and verification safeguards

Use cases

  1. 01Guiding an agent through travel tasks
  2. 02Requiring approval before payments or cancellations
  3. 03Avoiding plaintext credential handling

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/nomadamas/k-skill --skill mofa-travel-safety

After installing, type/mofa-travel-safetyin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

instruction.md
skill.json
scripts/
run_mofa_travel_safety.py

Details

From the project README

mofa-travel-safety

Get the full instructions (required first step)

Run this and follow its output as the primary instructions for this skill:

npx -y @nomadamas/k-skill@0 instruct mofa-travel-safety

The CLI detects the current runtime (Dolshoi vault/CloakBrowser vs generic) and prints only the applicable instructions, always up to date. Helper files bundled with the CLI are listed by:

npx -y @nomadamas/k-skill@0 files mofa-travel-safety

Keep the CLI and every coding-agent skill install current (including Vercel Agent Skills) with:

npx -y @nomadamas/k-skill@0 update

If npx is unavailable, install Node.js 18+ or follow https://github.com/NomaDamas/k-skill#readme, or read the source instructions at https://github.com/NomaDamas/k-skill/blob/main/mofa-travel-safety/instruction.md.

Hard rules even without the CLI

  • Never execute payment, message/email delivery, final submission, cancellation, or public posting without the user's explicit approval immediately beforehand.
  • Never ask for, print, or store plaintext credentials in chat, files, or shell arguments.
  • Never bypass legal, physical-presence, CAPTCHA, identity-proofing, or electronic-signature boundaries.

Comments

Markdown supported