ntfsmac: Instructions file for Claude Code

CLAUDE.md

ntfsmac CLAUDE.md is an instructions file for Claude Code from khr898/ntfsmac. It costs 2,316 tokens per session, scanned A, original, MIT.

Project instructions for ntfsmac, including its build order, software stack, environment, and required working rules.

In plain words
What is it for?
They help an agent follow the correct build order, use the intended environment and stack, and avoid revisiting settled project decisions.
Why use it?
They give a coding agent the project’s non-negotiable rules and setup details instead of leaving those decisions to guesswork.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code; mentions AGENTS.md.

This is khr898/ntfsmac's own configuration. It tells Claude Code how to work on ntfsmac 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 ntfsmac configures →

Reuse

Borrowing it

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

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 ntfsmac CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/khr898/ntfsmac/claude-md.svg)](https://agentmods.dev/instructions/khr898/ntfsmac/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/khr898/ntfsmac/claude-md"><img src="https://agentmods.dev/badge/instructions/khr898/ntfsmac/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,316 This file is loaded in full into every session.
When invoked 2,316 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.02316 $0.02316
Opus 5 $0.01158 $0.01158
Sonnet 5 $0.00463 $0.00463
Haiku 4.5 $0.00232 $0.00232

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

Security

Grade A, and why

ntfsmac 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 7d 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 · 82 lines

How it starts

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

ntfsmac

New here? README.md has install/usage; CONTRIBUTING.md has human setup steps. This file (mirrored at AGENTS.md) is AI-agent instructions — read it before generating code in this repo, human or agent.

NTFS read/write on Apple Silicon macOS, no kernel extension, no SIP modification. Wraps anylinuxfs (libkrun microVM running ntfs-3g, exported to macOS over NFS on a host-only vmnet bridge). CLI first, GUI second — build order is fixed, don't jump ahead.

Full spec: docs/dev/PLAN.md (architecture, phases, build steps) and docs/dev/GUI-PLAN.md (SwiftUI menu-bar app, button-level spec). Read the relevant phase section before writing code for it — don't work from memory of what these say. ui/prototype.html (the original static HTML/SVG design comp) was removed 2026-07-13 — the already-built SwiftUI screens are now the visual source of truth for colors, radii, spacing, and the vibrancy/blur recipe. Match what's already built; don't re-design.

Non-negotiables (do not re-litigate)

  • Driver: ntfs-3g default. ntfs3 is opt-in only via --fs-driver ntfs3, never via an -o token (it's inert there).
  • Transport: NFS only, over vmnet-helper host-only /30 bridge. No SMB. No loopback/127.94.0.1 design — that's dead, don't resurrect it.
  • NFS mount mode stays soft — never switch to hard, it's what prevents a kernel panic on hot-unplug.
  • Signing: ad-hoc only (codesign -s -). No paid Apple Developer account, no notarization. This is why the GUI is DMG-only (never a Homebrew cask) and the CLI is a formula in the project's own tap (never homebrew-core).
  • Every control that mounts/unmounts/touches pf/route goes through the SMJobBless XPC helper — never a raw sudo shell-out from Swift UI code.
  • Device names validated against ^disk[0-9]+s[0-9]+$ before any shell invocation, in both CLI and GUI/helper.
  • Platform: Apple Silicon only. Don't add Intel fallback paths.
  • Security and connection stability outrank speed. Speed tuning (rsize/wsize/async export) is opt-in and documented as risk, never silently defaulted on.

Read the full file on GitHub · 82 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. 7d ago First seen · 82 lines · 2,316 tokens per session scan A b1733e9cb498

Subscribe to this mod's changes

ntfsmac CLAUDE.md is an instructions file published in the GitHub repository khr898/ntfsmac (570 stars, last pushed 3d ago), licensed MIT. It adds 2,316 tokens to every session, about $0.0116 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.

Related

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.

vercel/next.js · 7,296 tokens

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

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

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

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