agentmods.dev

milady: Instructions file for Claude Code

CLAUDE.md

milady CLAUDE.md is an instructions file for Claude Code from milady-ai/milady. It costs 8,242 tokens per session, scanned A, original, MIT.

Project instructions for Claude Code when working on milady-ai/milady, a local-first AI assistant with a command line tool, desktop app, web dashboard, and platform connections.

In plain words
What is it for?
Use them when changing milady code, especially its cloud frontend or shared packages that affect the frontend.
Why use it?
They record the repository's conventions, development commands, naming rules, and required visual review process.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is milady-ai/milady's own configuration. It tells Claude Code how to work on milady itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything milady configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/shaw/milady.

not rated 357repo 17d ago A scan 8,242 tokens original MIT
View source ↗ milady-ai/milady milady.ai
Reuse

Borrowing it

Nothing to install: this file belongs to milady-ai/milady. 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/milady-ai/milady/develop/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/milady-ai/milady

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.

agentmods badge for milady CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/milady-ai/milady/claude-md.svg)](https://agentmods.dev/instructions/milady-ai/milady/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/milady-ai/milady/claude-md"><img src="https://agentmods.dev/badge/instructions/milady-ai/milady/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 8,242 This file is loaded in full into every session.
When invoked 8,242 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.08242 $0.08242
Opus 5 $0.04121 $0.04121
Sonnet 5 $0.01648 $0.01648
Haiku 4.5 $0.00824 $0.00824

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

Security

Grade A, and why

milady 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 8d 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.md · 668 lines

How it starts

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

Milady — Agent Conventions

Local-first AI assistant on elizaOS. CLI + desktop (Electrobun) + web dashboard + connectors.

Architecture commandments, QA protocol, git workflow: AGENTS.md. Sandbox/distribution: docs/sandbox-mode.md.

Naming

Write elizaOS (not ElizaOS). npm scope @elizaos/*. Plain language: Eliza agents. Exception: Eliza Classic plugin keeps Eliza (the 1966 chatbot).

Cloud frontend visual review (REQUIRED for any UI change)

Path/mode note: cloud-frontend lives at eliza/packages/cloud-frontend and is on disk only in local mode (bun run eliza:local). Every packages/cloud-frontend/… path in this section is relative to eliza/packages/cloud-frontend/.

For ANY change in eliza/packages/cloud-frontend/ (or any shared package whose UI bleeds into cloud-frontend), follow this loop until every touched page reaches verdict good:

bun run --cwd eliza/packages/cloud-frontend audit:cloud

This boots the dev server, performs an injected-ethereum login (synthetic JWT in localStorage.steward_session_token), visits every route in src/App.tsx at desktop + mobile, captures rest + hover screenshots, and writes:

packages/cloud-frontend/aesthetic-audit-output/
  desktop/<slug>.png            rest screenshot
  desktop/<slug>--hover.png     primary-button hover state
  mobile/<slug>.png
  mobile/<slug>--hover.png
  manual-review/<slug>.md       REQUIRED per-page verdict markdown (auto-stubbed)
  contact-sheet.html            grid index
  report.json                   machine-readable findings

The 5-loop grind:

  1. Run the audit.
  2. Open contact-sheet.html. Walk every affected page.
  3. Fill in the verdict in manual-review/<slug>.md: visual issues, color/hover violations, layout breaks, e2e gaps, good · needs-work · needs-eyeball · broken.
  4. Fix issues in source.
  5. Commit screenshots + reviews + fixes together.
  6. Re-run. Repeat until every page is good. Five loops is the floor for any meaningful redesign.

Read the full file on GitHub · 668 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.

  1. 8d ago First seen · 668 lines · 8,242 tokens per session scan A c687894547d5

Subscribe to this mod's changes

milady CLAUDE.md is an instructions file published in the GitHub repository milady-ai/milady (357 stars, last pushed 17d ago), licensed MIT. It adds 8,242 tokens to every session, about $0.0412 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.

Autonomous Agentsagentagent-skillsagentsclawdclawdbot
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens