OpenMicro CLAUDE.md

Project instructions for OpenMicro, an npm software project, covering how releases and release checks should be handled.

In plain words
What is it for?
Use them when preparing a release or merging a feature that will ship in a release.
Why use it?
They reduce mistakes around version changes, changelog updates, release tags, and required checks.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/stephenleo/openmicro/claude-md
Clone the repo
git clone --depth 1 https://github.com/stephenleo/OpenMicro
Per session 123 This file is loaded in full into every session.
When invoked 123 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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 $0.00123 $0.00123
Opus 5 $0.00062 $0.00062
Sonnet 5 $0.00025 $0.00025
Haiku 4.5 $0.00012 $0.00012

Measured 2d ago against content hash 6c2f9e84309c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

OpenMicro 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 2d 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.

Origin

This is a copy

100% identical to OpenMicro AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 7 lines

What it actually says

OpenMicro — project conventions

Releases

  • Release inside the parent PR: when a fix/feature PR is going to ship as a release, push the version bump (npm version X.Y.Z --no-git-tag-version) and CHANGELOG entry as a commit on that same PR — do not open a separate release PR. After the parent PR merges, tag vX.Y.Z on main and push the tag; the publish workflow handles npm.
  • Verification gate before any release commit: npm run typecheck && npm run lint && npm run format:check && npm test.
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. 2d ago First seen · 7 lines · 123 tokens per session scan A 6c2f9e84309c

Subscribe to this mod's changes

OpenMicro CLAUDE.md is an instructions file published in the GitHub repository stephenleo/OpenMicro (127 stars, last pushed 10d ago), licensed MIT. It adds 123 tokens to every session, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to OpenMicro AGENTS.md, differing in 0 lines, and is treated as a copy.