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.
npx agentmods add instructions/ara3d/ara3d-sdk/claude-mdgit clone --depth 1 https://github.com/ara3d/ara3d-sdkWrote 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/ara3d/ara3d-sdk/claude-md)<a href="https://agentmods.dev/instructions/ara3d/ara3d-sdk/claude-md"><img src="https://agentmods.dev/badge/instructions/ara3d/ara3d-sdk/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 | $0.00727 | $0.00727 |
| Opus 5 | $0.00364 | $0.00364 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
ara3d-sdk 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 4d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ara3d-sdk — agent guide (Plato-related)
This SDK consumes Plato output; it must build standalone without the Plato toolchain.
Plato compiler + stdlib source live in ../submodules/Plato (see its CLAUDE.md). Plan:
../docs/plato-execution-plan-2026-07-09.md; live work in ../tracker/. (docs/plato-roadmap.md
was superseded and archived 2026-07-16 — now docs/archive/plato-roadmap.md, historical only.)
C# style: before writing/editing handwritten C# (e.g. src/Ara3D.Geometry/), follow the
csharp-style skill — full reference ../docs/csharp-style-guide-for-agents.md, enforceable
subset in the root .editorconfig. Does NOT apply to generated/synced code (Plato.Generated/,
Plato.Intrinsics/, Ara3D.IO.SharpGLTF/).
Plato-related layout
src/Plato.Generated/— checked-in generated C# (V1, instance-member style). Produced by..\..\tools\regen-plato.ps1 -Apply; NEVER hand-edit (drift is diff-gated in CI).src/Plato.Intrinsics/— SYNCED COPY (see its README). Source of truth issubmodules/Plato/Plato.Intrinsics; sync viaregen-plato.ps1 -Apply. Never edit here.src/Ara3D.Geometry/— handwritten geometry algorithms layered on the generated code (imports both shared projects). Known name collisions with Plato solids:Sphere,Cylinder,Curves(resolved at V2 adoption). Organized into semantic subfolders (Primitives/, MeshConstruction/, SpatialQueries/, etc.; see its README.md folder map). Folders are organizational only — namespace stays flatAra3D.Geometry. Place new files in the matching domain folder, not the root.tests/Ara3D.SDK.GeometryTests— expected 15/15.tests/Ara3D.SDK.Benchmarks— BenchmarkDotNet baseline (baseline-2026-07-07.md); don't modify to measure new code — build scratch probes instead.tools/ApiSnapshot+tools/api-snapshot.ps1— deterministic public-API dump →docs/api/plato-generated-api-baseline.txt(8,907 lines). Re-run after any generated-surface change.- Conformance suites live in the Plato repo (
submodules/Plato/conformance), not here.
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.
- 4d ago First seen · 40 lines · 727 tokens per session scan A a5d09c23ee14
ara3d-sdk CLAUDE.md is an instructions file published in the GitHub repository ara3d/ara3d-sdk (41 stars, last pushed 15d ago), licensed MIT. It adds 727 tokens to every session, about $0.0036 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.