Borrowing it
Nothing to install: this file belongs to jirukouya/auRO-whisky-macOS-setup. 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/jirukouya/auRO-whisky-macOS-setup/main/CLAUDE.mdgit clone --depth 1 https://github.com/jirukouya/auRO-whisky-macOS-setupWrote 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/jirukouya/auro-whisky-macos-setup/claude-md)<a href="https://agentmods.dev/instructions/jirukouya/auro-whisky-macos-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/jirukouya/auro-whisky-macos-setup/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/jirukouya/auro-whisky-macos-setup/claude-md"><img src="https://agentmods.dev/badge/instructions/jirukouya/auro-whisky-macos-setup/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.01327 | $0.01327 |
| Opus 5 | $0.00664 | $0.00664 |
| Sonnet 5 | $0.00265 | $0.00265 |
| Haiku 4.5 | $0.00133 | $0.00133 |
Grade A, and why
auRO-whisky-macOS-setup 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 11d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project knowledge map
This file is an index, not content. Its only job: tell any reader (a fresh Claude Code/Codex session, the maintainer months from now, or an external contributor) where the actual information lives, so nothing gets missed by relying on memory alone.
Rule: before answering any "what have we already done / dealt with / decided about X" question for this project, check all four sources below — not just one or two.
The four places change history lives
-
git log(commit messages) — the most granular record, tied to each diff. Bug-fix/investigation commits should follow a Symptom / Ruled out / Root cause / Fix body structure (not just a one-line summary) — see the two best examples: commits38092d5andc1db2eb.Also check
git notes(git log --show-notes, orgit notes show <hash>) — 13 older commits that predate this commit-message framework had that same Symptom/Ruled out/Root cause/Fix detail retroactively attached as notes instead of rewriting already-pushed history. Notes don't show up in a plaingit logor a freshgit clone/git fetch— the ref (refs/notes/commits) has to be fetched explicitly:git fetch origin refs/notes/commits:refs/notes/commits, thengit log --show-notes. Easy to forget this ref exists at all if you don't already know to look for it — which is exactly the kind of gap this file exists to close. -
CHANGELOG.md— curated, per-version (Keep a Changelog format), human-facing "what changed and why" summary. This is the closest equivalent to a traditional changelog/troubleshooting summary — check it whenever comparing "what do we already have" against an external log or report. -
SKILL.md(each step's mandatory verification blocks) andTROUBLESHOOTING.md("Known open issues" + the Common Gotchas table, split out ofSKILL.mdat v0.19.0 — see "Standing constraints" below). Together these are the living current-state doc: symptoms, verification methods, and anything still unresolved. If a question is "is this still broken / how do we verify this," this is the first place to check, since it's the only layer that's actively kept in sync with the live install process.
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.
- 11d ago First seen · 97 lines · 1,327 tokens per session scan A 95cdfd6d1a26
auRO-whisky-macOS-setup CLAUDE.md is an instructions file published in the GitHub repository jirukouya/auRO-whisky-macOS-setup (5 stars, last pushed 11d ago), licensed MIT. It adds 1,327 tokens to every session, about $0.0066 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-31.
Other instructions, from other repositories
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.
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).
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.
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).