Borrowing it
Nothing to install: this file belongs to robcsaszar/frontend-kit. 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/robcsaszar/frontend-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/robcsaszar/frontend-kitWrote 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/robcsaszar/frontend-kit/agents-md)<a href="https://agentmods.dev/instructions/robcsaszar/frontend-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/frontend-kit/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/robcsaszar/frontend-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/robcsaszar/frontend-kit/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00917 | $0.00917 |
| Opus 5.5 | $0.00367 | $0.00367 |
| Sonnet 5.5 | $0.00183 | $0.00183 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
frontend-kit AGENTS.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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Mission
This repo publishes the frontend-kit skill collection: four independent skills under skills/<name>/, each covering one frontend implementation area (canvas, drag-and-drop, Svelte 5 / SvelteKit, SVG animation). There is no build, no tests, no runtime of its own. The deliverable is the contents of skills/*. This repo's purpose is publishing copies of skills for others to install into their own projects, not authoring net-new guidance from scratch. Changes should be judged by: would a stranger who installs one of these skills into an unrelated project get correct, generically useful frontend guidance out of it?
Layout convention
- One directory per skill under
skills/<name>/,name:in frontmatter matching the directory name exactly. - Each skill is self-contained: its own
SKILL.mdplus anyreferences/it needs. No skill depends on another skill in this collection being installed. - No skill in this collection ships a
scripts/directory. If one is ever added, it needs aSAFETY.mdat the repo root documenting what the script does, per the same convention used in this author's other skill repos.
Judgment boundaries
NEVER:
- Never let a copied skill's content leak repo-specific references back to Orakl (or any other single project it may have been sourced from): file paths, project names, internal conventions. These skills need to read as generic frontend guidance, usable in any codebase.
ASK:
- Ask before removing a skill from the collection.
- Ask before changing the license or copyright holder.
ALWAYS:
- When adding, removing, or renaming a skill: update the table in
README.mdin the same change.
Adding a skill
- Copy the skill's full directory (
SKILL.mdplusreferences/,assets/,scripts/as applicable) intoskills/<name>/, matching the frontmattername:to the directory name. - Grep the copy for any project-specific leakage (source repo name, absolute paths, internal doc references) before publishing; flag anything found rather than silently editing the skill's content.
- Add a row to the table in
README.md. - If the skill ships a script, add a
SAFETY.mdat the repo root and link it fromREADME.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.
- 1mo ago Changed · +29 lines · +418 tokens per session 21d3e160ae4a
- 1mo ago First seen · 31 lines · 499 tokens per session scan A 87d3b222cdbb
frontend-kit AGENTS.md is an instructions file published in the GitHub repository robcsaszar/frontend-kit (1 stars, last pushed 1mo ago), licensed MIT. It adds 917 tokens to every session, about $0.0037 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.