Agent skill

Rust Unsafe Boundaries

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants.

MITAuto-check passedDevelopment

Install Rust Unsafe Boundaries

skills CLI
$ npx skills add hashgraph-online/awesome-codex-plugins --skill rust-unsafe-boundaries -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hashgraph-online/awesome-codex-plugins rust-unsafe-boundaries --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/LVTD-LLC/skills/skills/rust-unsafe-boundaries .claude/skills/rust-unsafe-boundaries && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
rust-unsafe-boundaries
GitHub stars
1.3k
Token cost
~782 tokens
SKILL.md length
302 words
Files
3 (incl. references)
Skills in repo
714
Repo updated
First seen
Licence
MIT

At a glance

Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants.

  • Works in 7 steps: Try the safe design first. Check… → State the invariant that safe Rust… → Keep unsafe blocks tiny. Put runtime… → …
  • Reviewing unsafe code
  • SKILL.md covers Core Workflow, Boundary Rules, Documentation Pattern and Review Checklist
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Rust Unsafe Boundaries is an agent skill from hashgraph-online/awesome-codex-plugins. Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants. Use when writing, refactoring, or reviewing unsafe code, raw pointers, unsafe functions, unsafe traits, MaybeUninit, pointer aliasing, panic safety, Miri checks, or safe abstractions over unsafe internals.

Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/safety-invariants.md`). Compatibility notes: Codex, Claude Code, and other Agent Skills-compatible clients.

It sits in Development, covering Refactoring. It works with Rust. The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is MIT.

When your agent uses it

  • Reviewing unsafe code
  • Unsafe functions
  • Pointer aliasing
  • Safe abstractions over unsafe internals

Example prompts

  • “/rust-unsafe-boundaries”

Requirements

  • Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients.

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Try the safe design first. Check standard APIs, ownership restructuring,
  2. State the invariant that safe Rust cannot prove. If the invariant cannot be
  3. Keep unsafe blocks tiny. Put runtime checks and setup in safe code before the
  4. Add a // SAFETY: comment immediately before each unsafe block explaining
  5. Mark a function unsafe fn only when callers must uphold extra conditions.
  6. Enable or respect unsafe_op_in_unsafe_fn; unsafe operations inside unsafe
  7. Test normal behavior, boundary cases, panic paths, and drop behavior. Run

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are rust).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Codex, Claude Code, and other Agent Skills-compatible clients.

    From compatibility in the SKILL.md frontmatter.

Context cost

Rust Unsafe Boundaries loads about 782 tokens when it runs, and up to ~1.1k if it reads all its reference files. Until then it costs about 83 tokens; SKILL.md has 302 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~83
When it runs · the whole SKILL.md, loaded when a task matches
~782
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its MIT licence (© hashgraph-online). 302 words, ~782 tokens.

Download SKILL.mdSave it as .claude/skills/rust-unsafe-boundaries/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
rust-unsafe-boundaries
description
Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants. Use when writing, refactoring, or reviewing unsafe code, raw pointers, unsafe functions, unsafe traits, MaybeUninit, pointer aliasing, panic safety, Miri checks, or safe abstractions over unsafe internals.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.
license
MIT
metadata.version
0.1.0
metadata.displayName
Rust Unsafe Boundaries
metadata.category
Rust
metadata.tags
rust,unsafe,raw-pointers,memory-safety,miri

Rust Unsafe Boundaries

Use this skill to isolate unsafe Rust behind small, documented, testable boundaries. Unsafe code is acceptable only when a safe API cannot express the needed operation with acceptable correctness and performance.

Core Workflow

  1. Try the safe design first. Check standard APIs, ownership restructuring, iterators, synchronization primitives, and existing crates.
  2. State the invariant that safe Rust cannot prove. If the invariant cannot be written down, do not write unsafe code yet.
  3. Keep unsafe blocks tiny. Put runtime checks and setup in safe code before the block.
  4. Add a // SAFETY: comment immediately before each unsafe block explaining why every unsafe operation inside is valid.
  5. Mark a function unsafe fn only when callers must uphold extra conditions. Document those conditions in a # Safety section.
  6. Enable or respect unsafe_op_in_unsafe_fn; unsafe operations inside unsafe functions should still be wrapped in explicit unsafe blocks.
  7. Test normal behavior, boundary cases, panic paths, and drop behavior. Run Miri when the project supports it.

Boundary Rules

Read references/safety-invariants.md before adding or approving unsafe code.

  • Prefer private unsafe internals plus a safe public wrapper.
  • Prefer MaybeUninit<T> over deprecated or ad hoc uninitialized memory patterns.
  • Never create references from raw pointers unless validity, alignment, initialization, aliasing, and lifetime are all proven.
  • Do not use set_len, pointer arithmetic, or from_raw_parts without proving capacity, initialization, and ownership.
  • Make panic safety explicit when partially initialized values, manual drops, or length changes are involved.
  • Avoid static mut; prefer OnceLock, LazyLock, atomics, or locked state.

Documentation Pattern

rust
/// # Safety
///
/// `ptr` must be non-null, aligned for `T`, initialized, and valid for reads
/// for the returned lifetime. No mutable reference may alias the same value.
pub unsafe fn read_ref<'a, T>(ptr: *const T) -> &'a T {
    // SAFETY: The caller guarantees `ptr` satisfies the documented contract.
    unsafe { &*ptr }
}

Review Checklist

  • Every unsafe block has a local SAFETY explanation.
  • Every unsafe fn or unsafe trait has a # Safety contract.
  • Public safe APIs cannot be used to violate internal invariants.
  • Drop, panic, and early-return paths preserve initialization and ownership.
  • Tests or Miri cover the dangerous edge, not only the happy path.

© hashgraph-online, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in plugins/LVTD-LLC/skills/skills/rust-unsafe-boundaries of hashgraph-online/awesome-codex-plugins.

  • SKILL.md
  • agents/openai.yaml
  • references/safety-invariants.md

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Rust Unsafe Boundaries next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Rust Unsafe Boundaries compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Rust Unsafe Boundaries this skillhashgraph-online/awesome-codex-plugins1.3k—~782Automated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Rust Best Practicesfarm-fe/farm5.6k3 repos~1.1kAutomated safety check: PassMIT
RTK Rust Design Patternsrtk-ai/rtk83k—~1.9kAutomated safety check: PassApache-2.0
RTK Rust Code Simplifierrtk-ai/rtk83k—~1.1kAutomated safety check: PassApache-2.0
Rust Hygiene Audittsz-org/tsz577—~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Guide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook.

    5.6k GitHub starsUsed in 3 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Describes seven Rust design patterns for the RTK CLI filter modules, with when to use each, RTK examples, and notes on when a pattern is overkill.

    83k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Reviews RTK's Rust code for over-engineering and verbose patterns, applying idioms like iterator chains and early returns while protecting a specific list of constraints from being simplified away.

    83k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Run a deep DRY + code-hygiene audit of the Rust workspace and turn the findings into verified, deduplicated, hierarchical GitHub tech-debt issues.

    577 GitHub stars~1.5k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Coding Agent

    mastra-ai/mastra

    Authoring playbook for building agents that write, edit, review, or refactor code.

    29k GitHub stars~2.3k tokensUpdated today
    DevelopmentAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo
  • Anime Reaction Gif

    hashgraph-online/awesome-codex-plugins

    Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.

    1.3k GitHub stars~922 tokensUpdated today
    Auto-check passed
  • Calibredb

    hashgraph-online/awesome-codex-plugins

    Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).

    1.3k GitHub stars~1k tokensUpdated today
    Auto-check passed
  • Rust API Test Harness

    hashgraph-online/awesome-codex-plugins

    A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…

    1.3k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • Art

    hashgraph-online/awesome-codex-plugins

    Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…

    1.3k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Calle

    hashgraph-online/awesome-codex-plugins

    Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.

    1.3k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Game Balance Economy

    hashgraph-online/awesome-codex-plugins

    Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.

    1.3k GitHub stars~618 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Rust Unsafe Boundaries

What does Rust Unsafe Boundaries do?

Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants. Rust Unsafe Boundaries is an agent skill from hashgraph-online/awesome-codex-plugins. Isolate and review unsafe Rust behind small, documented, testable boundaries with explicit invariants.

When should I use Rust Unsafe Boundaries?

Rust Unsafe Boundaries fits situations like: reviewing unsafe code; unsafe functions; pointer aliasing; safe abstractions over unsafe internals.

How do I install Rust Unsafe Boundaries in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill rust-unsafe-boundaries -a claude-code`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/rust-unsafe-boundaries in hashgraph-online/awesome-codex-plugins) into .claude/skills/rust-unsafe-boundaries in your project. Claude Code loads it when a task matches its description.

How do I install Rust Unsafe Boundaries in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill rust-unsafe-boundaries -a codex`. Or copy the skill folder (plugins/LVTD-LLC/skills/skills/rust-unsafe-boundaries in hashgraph-online/awesome-codex-plugins) into .agents/skills/rust-unsafe-boundaries in your project. Codex loads it when a task matches its description.

Can I use Rust Unsafe Boundaries in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashgraph-online/awesome-codex-plugins --skill rust-unsafe-boundaries -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/rust-unsafe-boundaries, .gemini/skills/rust-unsafe-boundaries, .github/skills/rust-unsafe-boundaries and .opencode/skills/rust-unsafe-boundaries in your project.

What does Rust Unsafe Boundaries need to run?

SKILL.md names no scripts, command-line tools or credentials: Rust Unsafe Boundaries is instructions for the agent only. Compatibility (from SKILL.md): Codex, Claude Code, and other Agent Skills-compatible clients..

Does Rust Unsafe Boundaries access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Rust Unsafe Boundaries safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Rust Unsafe Boundaries use?

Rust Unsafe Boundaries is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Rust Unsafe Boundaries use?

About 782 tokens (SKILL.md is roughly 3.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 339 tokens, read only when the agent opens those files.

What are the alternatives to Rust Unsafe Boundaries?

Skills that share tags, products or a category with Rust Unsafe Boundaries: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Rust Best Practices (farm-fe/farm, 5.6k stars), RTK Rust Design Patterns (rtk-ai/rtk, 83k stars) and RTK Rust Code Simplifier (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rust Unsafe Boundaries?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.