About mfds-food-safety
mfds-food-safety is a coding-agent skill that provides instructions for food-safety tasks. Its CLI selects guidance for the detected runtime, while the skill sets boundaries around sensitive actions and credentials.
Key features
- 01Runtime-specific instructions via CLI
- 02Lists bundled helper files
- 03CLI and skill update command
- 04Approval required for sensitive actions
- 05Credential and verification safeguards
Use cases
- 01Load food-safety instructions for the current runtime
- 02Inspect helper files bundled with the skill
- 03Update the skill installation
- 04Check safeguards before regulated actions
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ nomadamas/ k-skill --skill mfds-food-safetyAfter installing, type/mfds-food-safetyin Claude Code to confirm it loaded.
Bundled files
References and scripts installed along with SKILL.md.
instruction.mdskill.jsonscripts/mfds_food_safety.pyDetails
From the project READMEmfds-food-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 mfds-food-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 mfds-food-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/mfds-food-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.