Borrowing it
Nothing to install: this file belongs to ClawEnable/html-artifact-best-practices. 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/ClawEnable/html-artifact-best-practices/main/AGENTS.mdgit clone --depth 1 https://github.com/ClawEnable/html-artifact-best-practicesWrote 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/clawenable/html-artifact-best-practices/agents-md)<a href="https://agentmods.dev/instructions/clawenable/html-artifact-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/clawenable/html-artifact-best-practices/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/clawenable/html-artifact-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/clawenable/html-artifact-best-practices/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.00638 | $0.00638 |
| Opus 5.5 | $0.00255 | $0.00255 |
| Sonnet 5.5 | $0.00128 | $0.00128 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
html-artifact-best-practices 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 2mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a content-only Agent Skill package for standalone HTML artifacts. The distributable skill lives in skills/html-artifact-guide/.
skills/html-artifact-guide/SKILL.mddefines triggers, workflows, output requirements, and anti-patterns.skills/html-artifact-guide/references/contains deeper guidance, including artifact patterns and the review checklist.skills/html-artifact-guide/assets/standalone-template.htmlis the baseline single-file HTML template.skills/html-artifact-guide/evals/trigger-scenarios.mddocuments manual trigger scenarios.scripts/validate-artifact.jsandtests/validate-artifact.test.jscover the validator.docs/design-rationale.md, localized READMEs, andCONTRIBUTING.mdsupport distribution and contribution context.
Build, Test, and Development Commands
There is no app build chain, install step, or runtime service. Use these checks before submitting changes:
node --test tests/validate-artifact.test.js
node scripts/validate-artifact.js skills/html-artifact-guide/assets/standalone-template.html tests/fixtures/valid-artifact.html
! rg "Replace with|<title></title>" skills/html-artifact-guide/assets tests/fixtures/valid-artifact.html
test "$(rg -c "expected_action" skills/html-artifact-guide/evals/trigger-scenarios.md)" -ge 20
git diff --check
For local installation testing, copy the skill contents with cp -r skills/html-artifact-guide/* ~/.codex/skills/html-artifact-guide/.
Coding Style & Naming Conventions
Most source files are Markdown. Use concise headings, direct instructions, and concrete pass/fail criteria. Keep examples framework-free: vanilla HTML, inline CSS, and vanilla JavaScript only. Do not reference React, Vue, Tailwind, CDNs, remote fonts, or external scripts. Use kebab-case filenames, such as review-checklist.md.
Testing Guidelines
Automated tests cover the validator with Node's built-in test runner. Manual review covers trigger behavior and content quality. When changing trigger language or the output contract, review SKILL.md, evals/trigger-scenarios.md, the template, the review checklist, and the validator for drift.
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.
- 2mo ago First seen · 45 lines · 638 tokens per session scan A 8d03bba19135
html-artifact-best-practices AGENTS.md is an instructions file published in the GitHub repository ClawEnable/html-artifact-best-practices (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 638 tokens to every session, about $0.0026 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.