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/yuri-semenenko/ai-engineering-workspace/frontendgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/frontend)<a href="https://agentmods.dev/instructions/yuri-semenenko/ai-engineering-workspace/frontend"><img src="https://agentmods.dev/badge/instructions/yuri-semenenko/ai-engineering-workspace/frontend.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.00157 | $0.00157 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
Frontend Standards 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.
What it actually says
Frontend Standards
Follow existing design system and component conventions.
Prefer:
- semantic HTML
- accessible controls
- predictable state flow
- stable layout dimensions for fixed-format UI
- clear loading, error, and empty states
- small focused components
Avoid:
- decorative complexity without product value
- component abstractions before repetition is real
- layout shifts from dynamic content
- text overflow or overlap
- hidden keyboard traps
For React, use hooks correctly and keep side effects explicit. Avoid duplicating derived state unless it is needed for interaction.
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 · 30 lines · 157 tokens per session scan A b3a3e07e94b8
Frontend Standards is an instructions file published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 6d ago), licensed MIT. It adds 157 tokens to every session, about $0.0008 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
loadout reactjs.instructions.md
ReactJS Engineering Instructions.
apm python.instructions.md
Python development guidelines.
apex-accelerator vendor-prompting.instructions.md
Vendor prompting best-practice rules for Anthropic Claude and OpenAI GPT-5.6-Terra agents and prompts. Each rule cites a rule ID in the vendor-prompting skill rules.json registry. Validator: npm run lint:vendor-prompting.
tanstack-start-template AGENTS.md
AGENTS.md instructions for dyeoman2/tanstack-start-template, covering tanstack start agent guide, core philosophy, architecture, golden rules and key patterns.
github-copilot-token-optimization copilot-instructions.md
Copilot instructions for olivomarco/github-copilot-token-optimization: Terse like caveman. Technical substance exact. Only fluff die. Drop: articles, filler (just/really/basically), pleasantries, hedging. Fragments OK. Short synonyms. Code unchanged. Pattern: [thing] [action] [reason]. [next step]. ACTIVE EVERY…
next-sanity CLAUDE.md
Claude Code instructions for sanity-io/next-sanity, a project described as: Sanity toolkit for Next.js.