Borrowing it
Nothing to install: this file belongs to sacloud/sakumock. 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/sacloud/sakumock/main/CLAUDE.mdgit clone --depth 1 https://github.com/sacloud/sakumockWrote 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/sacloud/sakumock/claude-md)<a href="https://agentmods.dev/instructions/sacloud/sakumock/claude-md"><img src="https://agentmods.dev/badge/instructions/sacloud/sakumock/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.1 | $0.03723 | $0.03723 |
| Opus 5 | $0.01861 | $0.01861 |
| Sonnet 5 | $0.00745 | $0.00745 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade A, and why
sakumock 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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sakumock
Service Conventions
The repository is a single Go module (github.com/sacloud/sakumock); each service is a package under its own subdirectory, and shared building blocks live in core/. Services must not import each other; shared code goes through core. All services are also aggregated into a single sakumock binary (cmd/sakumock) exposing each as a subcommand with the same flags as the standalone sakumock-<service> binary; only the unified binary is released (GoReleaser), per-service binaries stay go install-able.
Required public API
The contract is type-enforced: server.go asserts var _ core.ServiceConfig = Config{} and var _ core.Server = (*Server)(nil), so a drifting service fails to build.
Config— kong-tagged struct satisfyingcore.ServiceConfig:Name()(short name = subcommand, e.g."apprun-dedicated"),ListenAddr()(=Config.Addr),ClientEnv() []core.EnvVar(theSAKURA_ENDPOINTS_*override(s) a client sets to reach this mock — the single source for the env var name, used by startup logs,sakumock env, and service link),Doc()(=Doc),NewServer(opts core.ServerOptions)(applies the shared opts, adaptsNewHandler). Add a field tocore.ServerOptionsto inject a dependency into every service without changing the interface.Command— embedsConfig, addsRoutes bool/Docs boolandRun(ctx) error; shared by the standalone and unified binaries.--routesprints the route table,--docsthe embedded README, then exit.Doc string—README.mdembedded indoc.go.NewHandler(cfg Config) (*Server, error)— handler without listener (returnnilerror when construction cannot fail; keep the signature uniform).NewTestServer(cfg Config) *Server— starts anhttptest.Server(panics on error).*Serversatisfiescore.Server:http.Handler+Routes() []core.Route+TestURL()(""when built byNewHandler, never panics) +Close().
File structure
store.go(Store interface, domain types),store_memory.go,new_store.go(factory)handler.go— HTTP handlers and JSON typesroute.go—routeTable()is the single source of truth driving bothbuildMux()andRoutes()validate_gen.go+generate.go— generated validation tables and their//go:generatedirective;validate_overrides.gofor declared spec gapsserver.go— Config, Server, NewHandler, NewTestServercli.go—Command;Runsets up logging/tracing, prints routes/docs, or serves viacore.Serve, and holds the startup log linesdoc.go—//go:embed README.mdcmd/sakumock-<service>/— thin standalone entrypoint (core.NotifyContextfor signals)- Makefile, README.md,
openapi/
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.
- 3d ago Changed · -68 lines · -5,424 tokens per session 8a2e961431bc
- 7d ago First seen · 190 lines · 9,147 tokens per session scan A 026a6e868f58
sakumock CLAUDE.md is an instructions file published in the GitHub repository sacloud/sakumock (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 3,723 tokens to every session, about $0.0186 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
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.
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.
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 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).
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.