Borrowing it
Nothing to install: this file belongs to Aysnc-Labs/angora. 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/Aysnc-Labs/angora/main/CLAUDE.mdgit clone --depth 1 https://github.com/Aysnc-Labs/angoraWrote 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/aysnc-labs/angora/claude-md)<a href="https://agentmods.dev/instructions/aysnc-labs/angora/claude-md"><img src="https://agentmods.dev/badge/instructions/aysnc-labs/angora/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.00840 | $0.00840 |
| Opus 5 | $0.00420 | $0.00420 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
angora 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Angora
A design system and site builder. Tokens, components, and rendered specimens — the visual language as code. Add the SQLite content layer to turn the same components into a working prototype or a full static site.
Scope: Marketing sites — heroes, pricing, features, testimonials, CTAs, navigation, footers. Not app UI, not dashboards.
Build Layer
- Astro — build tool. Semantic HTML + Tailwind utility classes. No custom elements, no
@scopeCSS. - Tailwind CSS v4 — styling layer via
@tailwindcss/vite. Tokens insrc/styles/global.cssusing@theme. - Preact — interactive islands via
@astrojs/preact. Design system components are Astro (static HTML, zero JS) by default. Preact for client-side state (modals, accordions, dynamic forms) withclient:loadorclient:visible. - Drizzle ORM — database layer wrapping
better-sqlite3. Tables insrc/data/schema/tables/. - SQLite — content store at
src/data/data.sqlite, committed to git.
Key Files
| File | Purpose |
|---|---|
src/system.md |
Intent, accessibility standard, anti-patterns, decisions log |
src/styles/global.css |
@theme block with all design tokens — single source of truth |
src/styles/design-system.css |
Design system chrome (tooling, doesn't ship) |
src/components/*.astro |
Components — semantic HTML + Tailwind |
src/icons/ |
Icon components (no Icon prefix — directory provides context) |
src/pages/design-system/ |
Specimen pages, wireframes, layouts, full-screen views |
src/pages/*.astro |
Production site pages |
src/layouts/*.astro |
Site layouts (header/footer wrappers) |
src/data/schema/tables/ |
Drizzle table definitions (one file per table) |
src/data/schema/index.ts |
Barrel re-export of all tables |
src/data/db.ts |
Drizzle client (db) and raw driver (sqlite) |
src/data/migrations/ |
SQL migrations (generated, committed, never hand-edit) |
inbox/ |
Passive file queue for images, CSVs, JSON (gitignored) |
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.
- 6d ago First seen · 64 lines · 840 tokens per session scan A eb984a3d3178
angora CLAUDE.md is an instructions file published in the GitHub repository Aysnc-Labs/angora (6 stars, last pushed 4mo ago), licensed MIT. It adds 840 tokens to every session, about $0.0042 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).
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).
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.
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.