Borrowing it
Nothing to install: this file belongs to yakushstanislav/UltraViolet. 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/yakushstanislav/UltraViolet/master/CLAUDE.mdgit clone --depth 1 https://github.com/yakushstanislav/UltraVioletWrote 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/yakushstanislav/ultraviolet/claude-md)<a href="https://agentmods.dev/instructions/yakushstanislav/ultraviolet/claude-md"><img src="https://agentmods.dev/badge/instructions/yakushstanislav/ultraviolet/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.01550 | $0.01550 |
| Opus 5 | $0.00775 | $0.00775 |
| Sonnet 5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
UltraViolet 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 8d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UltraViolet Rules
Mandatory rules for the UltraViolet repository.
- The code-style rules below (lint, headers, imports, handler shape, DTO validation, SQL builder) apply to Go code under
service-api. - Frontend services (
service-frontend,service-documentation-frontend) follow their own lint/format setup. - The
Documentation (Mandatory)rule applies to every service in this repository.
Documentation (Mandatory)
Every change that adds or modifies user-visible or operator-visible functionality must update service-documentation-frontend/docs/ in the same commit / PR. Documentation drift is treated as a blocking defect on par with a failing lint.
Triggers
A doc update is required when a change touches any of the following:
| Change | Where to update |
|---|---|
| New or modified HTTP / WebSocket endpoint | docs/api/endpoints.md (full table) + the feature-area page that exposes it (docs/scanning/, docs/hosts/, docs/alerts/, …). |
| New or modified env-var | docs/deployment/env-reference.md (full table) + every feature page that references it. |
New or modified SQL migration under service-api/deploy/migrations/ |
docs/concepts/data-model.md (migrations list + tables + indexes). |
New protocol probe under service-api/internal/pkg/probe/ |
docs/probes/service-protocols.md (row with default ports + extracted fields). |
| New background worker, cron task, or retention policy | docs/concepts/ or docs/admin/retention.md, plus docs/api/metrics.md if it adds metrics. |
New or substantially changed UI route in service-frontend |
The matching user-facing page under docs/scanning/, docs/search/, docs/hosts/, docs/dashboard/, docs/alerts/, or docs/admin/. |
| RBAC, JWT, rate-limit, or bootstrap behaviour change | docs/concepts/rbac.md and/or docs/api/authentication.md. |
Change to service-env/docker-compose.yml, Makefile, install.sh, upgrade.sh, backup.sh, restore.sh, or related scripts |
The corresponding page under docs/deployment/. |
| Change to release archive contents, dist layout, or supported install modes | docs/deployment/offline-install.md. |
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.
- 8d ago First seen · 128 lines · 1,550 tokens per session scan A 3c30b7e0ab2b
UltraViolet CLAUDE.md is an instructions file published in the GitHub repository yakushstanislav/UltraViolet (44 stars, last pushed 18d ago), licensed MIT. It adds 1,550 tokens to every session, about $0.0077 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
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).
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.
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).
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.