applyer CLAUDE.md

applyer CLAUDE.md is an instructions file for Claude Code from xCirno1/applyer. It costs 744 tokens per session, scanned A, original, MIT.

A project instruction file for the xCirno1/applyer codebase, covering coding, interface design, performance, and response practices.

In plain words
What is it for?
Use it when developing or reviewing that codebase, especially frontend features, user actions, loading states, errors, and core-logic tests.
Why use it?
It gives agents consistent rules for validation, error handling, reusable components, responsive interfaces, and tests.

Instructions file for Claude Code

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

Install

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.

agentmods
npx agentmods add instructions/xcirno1/applyer/claude-md
Clone the repo
git clone --depth 1 https://github.com/xCirno1/applyer

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xcirno1/applyer/claude-md.svg)](https://agentmods.dev/instructions/xcirno1/applyer/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/xcirno1/applyer/claude-md"><img src="https://agentmods.dev/badge/instructions/xcirno1/applyer/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 744 This file is loaded in full into every session.
When invoked 744 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.00744 $0.00744
Opus 5 $0.00372 $0.00372
Sonnet 5 $0.00149 $0.00149
Haiku 4.5 $0.00074 $0.00074

Measured today against content hash 1a1ef2ed2481, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

applyer 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 today.

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 · 48 lines

How it starts

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

Code Guidelines

  • Always use production style and compatible code.
  • When developing frontend applications, always prioritize user experience (e.g. Use Skeletons when loading data/page, Spinner + disable when performing actions through a button, etc). And, always consider the layout of the page for mobile.
  • Always implement full features, do not use "TODO" or "Pending Implementation".
  • Never assume that any received data is valid, always verify. This means that if some data is malfunctioned, the app doesn't break and we receive proper logs.
  • Always create reusable UI components in a dedicated directory.
  • Use proper error handling for ALL code paths with possible errors.
  • Always write tests for core logic, capturing all path and edge-cases.

Design Guidelines

  • For buttons and other clickable elements, use cursor-pointer on hover.
  • Use toast notification for success, errors, or any other events.
  • Never use the browser's native confirm()/alert()/prompt() dialogs. Use a custom modal for yes/no confirmations (e.g. destructive actions) and a toast for one-way notifications.
  • Use tooltips for idiomatic, technical, and potentially unfamiliar words.
  • Instead of expanding down for more sections, try expanding to the right and left.
  • For collapsible components that require many actions/informations/fields, consider using modal/dedicated page instead.

Style Guidelines

  • Never use icons with background colors and rounded corners.
  • Never use blocky UI, i.e. Plain box with rounded corners with some data inside.
  • Never use chips with dot on the left side.
  • Prioritize rectangle buttons rather than pills.
  • Don't hand-tune radii, type sizes, or spacing to taste.
  • Don't use em-dashes.
  • Density is a feature. Controls are fixed-height (h-6/h-7), table rows are py-1.5, panel padding is px-3. Whitespace between sections should be smaller than you'd use on a content page.
  • Depth comes from 1px seams and the surface ramp (bg-inset < bg < bg-soft < bg-raised), not from shadows, glows, translucency, or backdrop-blur. Panel fills are opaque and panel edges use full-strength border-border; border-border-soft is for dividers inside a panel. The only two shadows are shadow-pop (popovers) and shadow-overlay (modals) — both for things that genuinely float.
  • Chrome should sit still. The top bar and the workspace rail are opaque bands with hard seams, and everything positioned against the top bar reads its height from the nav spacing token (--nav-h) rather than restating it.

Read the full file on GitHub · 48 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. today Changed · +1 lines · -2 tokens per session 1a1ef2ed2481
  2. 5d ago First seen · 47 lines · 746 tokens per session scan A 496a407109cc

Subscribe to this mod's changes

applyer CLAUDE.md is an instructions file published in the GitHub repository xCirno1/applyer (7 stars, last pushed yesterday), licensed MIT. It adds 744 tokens to every session, about $0.0037 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.

Related

Other instructions, from other repositories