Borrowing it
Nothing to install: this file belongs to mollyretter/forward-deployed-engineer-toolkit. 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/mollyretter/forward-deployed-engineer-toolkit/main/CLAUDE.mdgit clone --depth 1 https://github.com/mollyretter/forward-deployed-engineer-toolkitWrote 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/mollyretter/forward-deployed-engineer-toolkit/claude-md)<a href="https://agentmods.dev/instructions/mollyretter/forward-deployed-engineer-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/mollyretter/forward-deployed-engineer-toolkit/claude-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/mollyretter/forward-deployed-engineer-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/mollyretter/forward-deployed-engineer-toolkit/claude-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.00479 | $0.00479 |
| Opus 5.5 | $0.00192 | $0.00192 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
forward-deployed-engineer-toolkit 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 2mo 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working in this repo
Notes for agents (Claude Code) collaborating on forward-deployed-engineer-toolkit. Project-level guidance; user-level writing preferences live in user memory.
Commit and PR conventions
- One gitmoji per commit (unicode preferred, e.g. ✨, ♻️, 🐛, 📋). Do not double up emoji and text code.
- PRs go through
gh pr reviewwith explicit dev approval before any review comment posts publicly.
Skill conventions
- Each skill ships in two shapes: a Claude Code skill (
SKILL.md) and an importable schema/library (schema.tsplus tests). - New skills should follow the directory shape of
skills/north-star/(the prior art). validate-skills.mjsandvitestrun in CI on every PR; both must be green before merge.
Privacy: CI stdout is public, braintrust is private
This repo is public. GitHub Actions logs are public. Braintrust traces are private. Anything any CI script prints to stdout or stderr is durably public.
Rules for CI scripts that touch braintrust data:
- Eval scripts, telemetry scripts, and threshold-check scripts may print only aggregate numbers (counts, precision, recall, percentages, averages). Never:
- PR diff content, even partial
- Agent prompts or responses, even partial
- Finding text, location strings that reference real files, or suggestion text
- Dev decision content (the labels themselves, beyond aggregate counts)
- Any field of a logged trace beyond the trace ID
- If a script needs to indicate which traces it processed, print trace IDs only. Anyone with braintrust access can look up the content; anyone without it sees only opaque identifiers.
- On API errors: print a sanitized error message (e.g.
braintrust API error: status 429), never the request or response bodies. - When in doubt, do not print. Add a comment explaining why a field is intentionally redacted so future maintainers do not "fix" it.
This rule applies to every script under scripts/ and every workflow under .github/workflows/. Skill files (SKILL.md) repeat the rule for the agent's benefit during interactive runs, but the canonical statement is here.
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.
- 2mo ago First seen · 33 lines · 479 tokens per session scan A ddd6b645ef5a
forward-deployed-engineer-toolkit CLAUDE.md is an instructions file published in the GitHub repository mollyretter/forward-deployed-engineer-toolkit (11 stars, last pushed 2mo ago), licensed MIT. It adds 479 tokens to every session, about $0.0019 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-08-31.
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.