Borrowing it
Nothing to install: this file belongs to AmethystLuna/embedded-workbench. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AmethystLuna/embedded-workbench/master/AGENTS.mdgit clone --depth 1 https://github.com/AmethystLuna/embedded-workbenchWrote 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/amethystluna/embedded-workbench/agents-md)<a href="https://agentmods.dev/instructions/amethystluna/embedded-workbench/agents-md"><img src="https://agentmods.dev/badge/instructions/amethystluna/embedded-workbench/agents-md/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.
<a href="https://agentmods.dev/instructions/amethystluna/embedded-workbench/agents-md"><img src="https://agentmods.dev/badge/instructions/amethystluna/embedded-workbench/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02719 | $0.02719 |
| Opus 5.5 | $0.01088 | $0.01088 |
| Sonnet 5.5 | $0.00544 | $0.00544 |
| Haiku 4.5 | $0.00272 | $0.00272 |
Grade A, and why
embedded-workbench AGENTS.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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Agent and contributor guide for the Embedded Engineering Workflow plugin. This
file is the single source. CLAUDE.md only points here, because Claude Code looks
for that name by convention.
Writing Rules
These apply to every file this repository ships, injects or publishes, and to the text of a store entry. They come from the review that produced the current text.
- Short sentences, one idea each. The reader does not have the author's context. A sentence that needs a second clause to make sense should be two.
- No brittle counts. Never write how many tools, checks, skills or agents exist. A release changes the number and the sentence silently becomes wrong. Name the thing instead.
- One job per file. Injected text is a guide to working in this plugin. A
SKILL.mdcarries doctrine and routing.agents/*defines one agent role.references/*.mdcarries per-domain detail. The README tells the human story. Manifests describe capability.DSH-COMPATIBILITY.mdholds measured evidence. State a fact in one place and point at it from everywhere else. - No dangling pointers. Every path, flag, skill and tool a file names must exist and be reachable from that file. A named command that no artifact implements is worse than no mention: the reader goes looking for it. Paths resolve from where the reader runs, not from the plugin root.
- Spend the budget. Injected text is paid once per session and mode context once per turn. Keep the top level lean and put detail behind a pointer.
- Say what it does not prove. Every scope claim needs its non-goal beside it. A diagnostic that narrows a fault has not localized it, and the text must say so.
- Injection carries the gate, not the enforcement scaffolding. The payload is
the Plan Verification Gate plus the context-budget rule. The 1% Rule and the Red
Flags table live in the
embedded-workbenchskill body, where a model that needs discipline can load them. They left the payload because capable models follow enforcement prompts literally — rigid phases, extra questions and 10–15× fan-out; the README links the reports. Do not put them back. - Descriptions stay factual. Store and manifest descriptions state what the plugin does. Slogans live in the README and the injected text, never in an entry description.
- Bilingual pairs move together. A Chinese document and its English counterpart change in the same commit.
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 · 192 lines · 2,719 tokens per session scan A 1d97e46bb933
embedded-workbench AGENTS.md is an instructions file published in the GitHub repository AmethystLuna/embedded-workbench (19 stars, last pushed today), licensed MIT. It adds 2,719 tokens to every session, about $0.0109 per session on Opus 5.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-10-12.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).