Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/mandarwagh9/embedist/claude-mdgit clone --depth 1 https://github.com/mandarwagh9/embedistWrote 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.
[](https://agentmods.dev/instructions/mandarwagh9/embedist/claude-md)<a href="https://agentmods.dev/instructions/mandarwagh9/embedist/claude-md"><img src="https://agentmods.dev/badge/instructions/mandarwagh9/embedist/claude-md.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00992 | $0.00992 |
| Opus 5 | $0.00496 | $0.00496 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
embedist CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repo layout note
The app root is this directory (embedist/embedist). The parent folder embedist/ is only a container — do not run npm/cargo from there. A separate Docusaurus package lives in docs/ with its own package.json; only run its scripts when editing docs.
AGENTS.md in this directory contains overlapping developer notes; keep both in sync when behavior changes.
Commands
Frontend scripts (package.json):
npm run dev— Vite dev server (port 1420, required bytauri.conf.json)npm run build—tsc && vite build(runs TypeScript strict-mode check)npm run tauri dev— run the full desktop app in developmentnpm run tauri build— produce release artifacts
There is no lint or test npm script. No automated test suite exists (*.test.*, *.spec.*, src-tauri/tests are all absent). Validation = npm run build + cargo clippy --manifest-path src-tauri/Cargo.toml + manual app checks.
Release artifacts from npm run tauri build:
- Portable:
src-tauri/target/release/embedist.exe - Installer:
src-tauri/target/release/bundle/nsis/Embedist_<version>_x64-setup.exe(NSIS only — set bytauri.conf.jsonbundle.targets)
Release version sync
When bumping the version, update all three files — they're independent and drift silently:
package.jsonsrc-tauri/Cargo.tomlsrc-tauri/tauri.conf.json
Architecture
Tauri 2 desktop app (Windows-only target). React 18 + TypeScript (strict) frontend talks to a Rust backend via Tauri invoke commands.
Frontend entry: src/main.tsx → src/App.tsx. State lives in Zustand stores under src/stores/ (aiStore, fileStore, settingsStore, uiStore) with localStorage persistence. Business logic is in hooks (src/hooks/use*.ts).
Backend entry: src-tauri/src/main.rs → src-tauri/src/lib.rs. All Tauri commands are registered in the invoke_handler! macro in lib.rs and implemented in src-tauri/src/commands/{ai,filesystem,platformio,pty,serial}.rs. Shared async state (SerialState, AIState, BuildState, PtyState, WatchState) is attached via .manage() in lib.rs — add new state there.
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.
- 5d ago First seen · 53 lines · 992 tokens per session scan A 9a164d5abcdc
embedist CLAUDE.md is an instructions file published in the GitHub repository mandarwagh9/embedist (47 stars, last pushed 3mo ago), licensed MIT. It adds 992 tokens to every session, about $0.0050 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.
Other instructions, from other repositories
kernel_chat GEMINI.md
Instructions for Ravi-Teja-konda/kernel_chat, covering building and running, writing tests, test structure and framework, mocking (vi from vitest) and commonly mocked modules.
memvid CLAUDE.md
Claude Code instructions for memvid/memvid, covering claude.md, project overview, architecture, core components and file format (.mv2).
FastLED GEMINI.md
Gemini CLI instructions for FastLED/FastLED, a project described as: The FastLED library for colored LED animation on Arduino. Please direct questions/requests for help to the FastLED Reddit community: http://fastled.io/r We'd like to use github "issues" just for tracking library bugs / enhancements.
monkey AGENTS.md
Instructions for monkey/monkey, covering agents, repository map, main runtime flow, build and verification and commit style used in this repository.
p3a CLAUDE.md
Claude Code instructions for fabkury/p3a, covering claude.md and claude code notes.
mspm0-skill AGENTS.md
Instructions for mc3545dada/mspm0-skill, covering repository agent instructions, repository rules, validation and documentation.