vellum-boundary-guard SKILL.md skillA
vellum-boundary-guard from vellum-ai/vellum-assistant is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vellum-ai/vellum-assistant/vellum-boundary-guard@git:20260521.b4bdd7aPins git:20260521.b4bdd7a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vellum-ai/vellum-assistant
- Path
.cursor/skills/vellum-boundary-guard/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260521.b4bdd7a, committed May 21, 2026
- Size
- 1,999 bytes
- Repository stars
- 1,467
- License
- MIT
Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Vellum Boundary Guard ## Package Import Boundaries Enforce these boundaries: - `assistant/` must not import from `gateway/` via relative paths. - `gateway/` must not import from `assistant/` via relative paths. - `assistant/` and `skills/` must not import from each other directly. - Runtime code must not import from `meta/`. - Shared cross-package logic belongs in `packages/`. For tests that need behavior from another package, mock the boundary instead of importing real handlers. ## HTTP And IPC Boundaries - Public inbound HTTP endpoints belong in `gateway/`. - New CLI-to-assistant interactions should use Unix socket IPC through the existing IPC route pattern. - Events from assistant runtime code should use the assistant event hub rather than new HTTP endpoints when possible. ## Security Ownership Boundaries - Gateway owns trust rules and gateway security files. - CES owns credential files. - The assistant must not read gateway-owned directories directly. - Clients must not read from the user's `~/.vellum` directory. - Secrets must not be stored in workspace files. ## Skill Boundaries …
Read the whole file at its exact version.
How to install
mdr add vellum-ai/vellum-assistant/vellum-boundary-guard@sha256:a6478f99453eccc9The line at the top of this page pins the label git:20260521.b4bdd7a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_i3mf57r6gas7evup)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 21, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1999 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vellum-ai/vellum-assistant · 1,467 stars · license MIT · pushed 2026-10-29 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i3mf57r6gas7evup GET https://markdownregistry.com/api/v1/resolve?ref=vellum-ai/vellum-assistant/vellum-boundary-guard GET https://markdownregistry.com/api/v1/blob/a6478f99453eccc908d5b88e1d568d81d0254fb3fbf8687b22c598ff2f3cbb1f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.