Borrowing it
Nothing to install: this file belongs to purupurupu/css-noop-checker. 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/purupurupu/css-noop-checker/main/AGENTS.mdgit clone --depth 1 https://github.com/purupurupu/css-noop-checkerWrote 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/purupurupu/css-noop-checker/agents-md)<a href="https://agentmods.dev/instructions/purupurupu/css-noop-checker/agents-md"><img src="https://agentmods.dev/badge/instructions/purupurupu/css-noop-checker/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.01110 | $0.01110 |
| Opus 5 | $0.00555 | $0.00555 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
Grade A, and why
css-noop-checker 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 8d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Agent Instructions
Human contributors: see CONTRIBUTING.md for the full contributor guide.
This file provides context for AI coding agents (Cursor, Copilot, Windsurf, etc.) working in this repository.
Project Structure
src/
rules/ Detection rules + engine, registry, context, types
sidebar/ DevTools sidebar React UI (see src/sidebar/ for details)
devtools.ts Extension entrypoint — creates the sidebar pane
e2e/
helpers/ Playwright extraction helpers (shared with MCP server)
integration/ Browser integration tests against examples/test.html
mcp-server/ Standalone MCP server (separate package.json, pnpm workspace)
examples/
test.html Test cases for all rules — used by both manual testing and e2e
public/
manifest.json Chrome extension manifest (MV3)
Adding a New Rule
This is the most common type of contribution. Follow these steps:
1. Create the rule file
Add src/rules/<target>-no-<qualifier>.ts. The filename is the rule ID.
Rule IDs follow Stylelint's thing-no-qualifier convention (e.g. inline-no-dimensions, container-no-gap).
import type { RuleContext, Warning } from './types.ts';
import { registerRule } from './registry.ts';
registerRule({
id: '<target>-no-<qualifier>',
label: '<short human-readable description>',
requiredProperties: ['<css-prop-1>', '<css-prop-2>'],
// requiredParentProperties: [], // optional, if parent styles are needed
check(ctx: RuleContext): Warning[] {
// Return warnings for properties that have no effect
return [];
},
});
2. Register in engine.ts
Add a side-effect import at the top of src/rules/engine.ts (keep alphabetical order):
import './<target>-no-<qualifier>.ts';
3. Add test cases to examples/test.html
Add both "should warn" and "should NOT warn" cases. Sections are ordered alphabetically by rule ID.
<!-- should warn -->
<div class="case expect-warn" data-rule="<rule-id>">
<div class="label label-warn"><rule-id> warn: description</div>
<div data-target style="...">example</div>
</div>
<!-- should NOT warn -->
<div class="case expect-ok" data-rule="<rule-id>">
<div class="label label-ok"><rule-id> ok: description</div>
<div data-target style="...">example</div>
</div>
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.
- 8d ago First seen · 119 lines · 1,110 tokens per session scan A 823331ee9c16
css-noop-checker AGENTS.md is an instructions file published in the GitHub repository purupurupu/css-noop-checker (24 stars, last pushed 5mo ago), licensed MIT. It adds 1,110 tokens to every session, about $0.0056 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-30.
Other instructions, from other repositories
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).
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.
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 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).
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.