agentmods.dev

fury3d: Instructions file for Claude Code

CLAUDE.md

fury3d CLAUDE.md is an instructions file for Claude Code from sindney/fury3d. It costs 477 tokens per session, scanned A, original, MIT.

A repository instruction file that tells Claude Code and other coding agents how to edit the Fury3D codebase, including rules for comments, naming, formatting, and keeping changes focused.

In plain words
What is it for?
Use it when asking an agent to modify or review code in the Fury3D repository.
Why use it?
It gives an agent the project's local conventions before it changes code, reducing unwanted rewrites, stale comments, and inconsistent style.

Instructions file for Claude Code

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

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

not rated 92repo yesterday A scan 477 tokens original MIT
View source ↗ sindney/fury3d
Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sindney/fury3d/claude-md/github.svg)](https://agentmods.dev/instructions/sindney/fury3d/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/sindney/fury3d/claude-md"><img src="https://agentmods.dev/badge/instructions/sindney/fury3d/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.

agentmods 80×15 button for fury3d CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sindney/fury3d/claude-md"><img src="https://agentmods.dev/badge/instructions/sindney/fury3d/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 477 This file is loaded in full into every session.
When invoked 477 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.00477 $0.00477
Opus 5.5 $0.00191 $0.00191
Sonnet 5.5 $0.00095 $0.00095
Haiku 4.5 $0.00048 $0.00048

Measured 1mo ago against content hash b3eaf3a2dc1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fury3d 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 1mo 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 · 26 lines

What it actually says

CLAUDE.md

Notes for Claude Code (and other coding agents) working in this repo.

Code style: comments

Write code as if it was always correct, then stop.

  • No history in comments. No "previously X did Y so now we do Z", no "this fixes a bug where...", no "legacy" or "new" labels on code paths. The current code is the code.
  • One-liners or none. Either a short single-line note above a non-obvious line, or no comment at all. Don't restate what the API name already says. No multi-paragraph essays.
  • Drop workarounds, then forget. When removing a workaround, don't leave a comment explaining what it replaced. The replacement is self-evident from the code.
  • Rename, don't annotate. If a function name no longer reflects what it does, rename it. Don't keep the stale name and add a comment.
  • ASCII only. No em-dash, arrows, smart quotes, degree signs, multiplication sign, or ellipsis. Use -, ->, '...', deg, x, ....

Code style: structure

  • Match the surrounding code's density, naming, and idiom. Don't restyle adjacent code.
  • Keep changes minimal and scoped to the task. No drive-by refactors.
  • Comments are facts, not narratives. If a comment is needed, it states what the code does or why a non-obvious choice exists — not how the code was reached.

Working in this repo

  • OpenSpec: changes live in openspec/changes/<name>/ with proposal.md, design.md, specs/, tasks.md. Use openspec status --change <name> --json and openspec instructions apply --change <name> --json to drive /opsx:apply.
  • Tests: tests/lua/*.lua invoked headlessly via ./fury exec <scene> <script.lua> from examples/.
  • Build dirs: build/ (normal), build-asan/ (AddressSanitizer). Don't ship binaries from these — examples/fury and examples/furye are the outputs.
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. 1mo ago First seen · 26 lines · 477 tokens per session scan A b3eaf3a2dc1c

Subscribe to this mod's changes

fury3d CLAUDE.md is an instructions file published in the GitHub repository sindney/fury3d (92 stars, last pushed yesterday), licensed MIT. It adds 477 tokens to every session, about $0.0019 per session on Opus 5.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-09-15.

3d-engineClaude CodeWriting and docscpp17imguirapidjsonsfml
Related

fury3d CLAUDE.md compared with instructions from other repositories

fury3d CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
fury3d CLAUDE.mdsindney/fury3dInstructions file92yesterdayMITA477Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode