Borrowing it
Nothing to install: this file belongs to 224-Industries/webflow-skills. 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/224-Industries/webflow-skills/main/AGENTS.mdgit clone --depth 1 https://github.com/224-Industries/webflow-skillsWrote 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/224-industries/webflow-skills/agents-md)<a href="https://agentmods.dev/instructions/224-industries/webflow-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/224-industries/webflow-skills/agents-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.00911 | $0.00911 |
| Opus 5 | $0.00456 | $0.00456 |
| Sonnet 5 | $0.00182 | $0.00182 |
| Haiku 4.5 | $0.00091 | $0.00091 |
Grade A, and why
webflow-skills 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 6d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
224 Industries - Webflow Agent Skills Repository
AGENTS.md (Symlink to CLAUDE.md)
This repo contains Webflow Agent Skills — folders of instructions, references, scripts, and assets that AI agents use to work more accurately with the Webflow ecosystem. For detailed architecture, see ARCHITECTURE.md.
Repo Structure
manifest.json # Root source of truth — global config + skills array
skills/
├── index.json # Generated — agent-skills-discovery RFC index
└── <skill-name>/
├── SKILL.md # Entry point — frontmatter + overview + reference index
├── references/ # Detailed reference docs (API guides, guidelines, etc.)
├── scripts/ # Helper scripts for the skill
└── assets/ # Static assets (CSS, images, etc.)
Reference File Conventions
Every file in references/ must have YAML frontmatter with three fields:
---
name: "Human-Readable Title"
description: "One-line summary of the file's contents."
tags: [tag1, tag2, tag3]
---
- name: Descriptive title (e.g., "Elements API", "Marketplace Guidelines")
- description: Single sentence summarizing what the file covers
- tags: Array of searchable keywords — include API method names, category terms, and key concepts
Content style
- Plain markdown only — no JSX components (
<Tabs>,<Steps>,<Note>,<Frame>, etc.) - Use fenced code blocks with language identifiers (e.g.,
```typescript) - Use markdown tables for structured data
- Use blockquotes (
>) for callouts and notes - End each reference with a "Best Practices" section where applicable
- Keep references focused on one API domain or topic per file
When adding references from external docs
Source documentation (e.g., Webflow's official docs) often uses JSX/HTML components. Strip these when converting:
| Source component | Convert to |
|---|---|
<Tabs> / <Tab> |
Separate sections with ### headings |
<Note> / <Warning> |
Blockquote (>) |
<Steps> / <Step> |
Numbered list with ### sub-headings |
<Accordion> |
Standard markdown table or section |
<Frame> / <img> |
Remove (image URLs won't resolve in this context) |
<Button> / <a> |
Inline markdown link |
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.
- 6d ago First seen · 98 lines · 911 tokens per session scan A 2e02706a1b08
webflow-skills AGENTS.md is an instructions file published in the GitHub repository 224-Industries/webflow-skills (9 stars, last pushed 24d ago), licensed MIT. It adds 911 tokens to every session, about $0.0046 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
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.
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).
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).
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.
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.