A crate-scaffolding tool for adding a new member to a Rust Cargo workspace, using the repository's `y5-template` and naming rules.

It helps create a new crate, module, or workspace member and link it into the repository's Cargo workspaces.

It avoids hand-writing the new crate files and prevents workspace wiring or chain-based directory names from being missed.

How y5-snowies/nourish configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to y5-snowies/nourish. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/y5-snowies/nourish/upstream-integration/.claude/skills/add-crate/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/y5-snowies/nourish

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/y5-snowies/nourish/add-crate/github.svg)](https://agentmods.dev/skills/y5-snowies/nourish/add-crate)

Your own site

<a href="https://agentmods.dev/skills/y5-snowies/nourish/add-crate"><img src="https://agentmods.dev/badge/skills/y5-snowies/nourish/add-crate/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/y5-snowies/nourish/add-crate"><img src="https://agentmods.dev/badge/skills/y5-snowies/nourish/add-crate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,524 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00074	$0.01524
Opus 5	$0.00037	$0.00762
Sonnet 5	$0.00015	$0.00305
Haiku 4.5	$0.00007	$0.00152

Measured 11d ago against content hash d8d1614ea5bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

add-crate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/add-crate/SKILL.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

add-crate

Scaffold a new member crate into a Cargo workspace using y5-template (on PATH at ~/.cargo/bin/y5-template; source in environment/toolkit/y5-template/). Do NOT hand-create Cargo.toml/lib.rs by hand — use the tool so naming and the template stay correct.

ALWAYS run compositor.workspace/link.all.sh from the repo root after creating a crate (step 5) — the crate is not wired into the workspaces until you do.

The naming convention (chain-prefix)

A crate is created exactly two levels below a workspace root, and each level's directory name chains off its parent: {parent_tail}.{own_segment}.

compositor/                  workspace root  (Cargo.toml [workspace] members glob has ≥2 `*`)
  compositor.action/         L0   (root_tail "compositor" + "action")
    action.window/           L1 = the target directory
      window.{Name}/         L2 = what the tool CREATES

root_tail = last dot-segment of the workspace dir name (compositor → compositor).
A valid L0 is {root_tail}.{seg}, a valid L1 is {seg}.{sub}.
The created dir is {L1_own_segment}.{Name} and must not already exist.

Steps

Find valid targets (the L1 dirs you can add into):
```
y5-template --scan /workspace --list
```
This prints every valid <workspace> › <L0> › <L1> with its absolute path.
Create the crate non-interactively. The picker needs a TTY, so use --dir (which skips the picker when the dir validates) and pipe the Name to stdin:
```
printf 'NAME\n' | y5-template --dir /workspace/compositor/compositor.action/action.window
```
- NAME becomes the crate suffix → creates window.NAME/.
- Batch: printf 'a, b, c\n' | y5-template --dir <L1_DIR> creates window.a, window.b, window.c atomically (aborts if any already exists).
- Extra template vars: if the chosen template declares vars beyond Name, they are prompted after Name — feed them as additional lines: printf 'NAME\nval1\nval2\n' | y5-template --dir <L1_DIR>. Check first with: y5-template --template <NAME> --help is not enough — inspect the template under <workspace>/y5.template/<tpl>/ for $${var}$$ placeholders.
- --template <NAME> selects a non-default template (default is default).

Read the full file on GitHub · 118 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 118 lines · 74 tokens per session scan A d8d1614ea5bc

Subscribe to this mod's changes

add-crate is a skill published in the GitHub repository y5-snowies/nourish (228 stars, last pushed 7d ago), licensed Apache-2.0. It adds 74 tokens to every session and 1,524 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Languages Rust compositor linux operating-system wayland

learn-rust

Use when the user wants to learn Rust interactively by exploring the sessions-chronicle codebase, guided by questions, micro-exercises, and Rust Book references.

supermaciz/sessions-chronicle · 36 tokens

typetype-development

TypeType development workflow, environment setup, testing, building, CI, and pre-commit checks. Use when setting up or preparing code for commit.

whynusn/typetype · 34 tokens

rust-patterns

Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.

affaan-m/ECC · 28 tokens

dd-code-generation

Use pup CLI for immediate Datadog operations or generate code for integration into applications.

DataDog/pup · 16 tokens

omh-rust

This is a Hermes-native rust workflow skill.

rlaope/oh-my-hermes · 69 tokens

create-skill

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

warpdotdev/warp · 64 tokens

nourish: Skill for Claude Code