Borrowing it
Nothing to install: this file belongs to richardcarls/solid-js-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/richardcarls/solid-js-best-practices/main/AGENTS.mdgit clone --depth 1 https://github.com/richardcarls/solid-js-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/richardcarls/solid-js-best-practices/agents-md)<a href="https://agentmods.dev/instructions/richardcarls/solid-js-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/richardcarls/solid-js-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/richardcarls/solid-js-best-practices/agents-md"><img src="https://agentmods.dev/badge/instructions/richardcarls/solid-js-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.00619 | $0.00619 |
| Opus 5.5 | $0.00248 | $0.00248 |
| Sonnet 5.5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
solid-js-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 18d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solid.js Best Practices - Contributor Guide
For AI agents: The primary skill content is in SKILL.md, which includes the rule index and task-based rule selection; the rule files carry examples and React comparisons.
This document is for contributors working on the skill itself.
Skill File Structure
solid-js-best-practices/
├── SKILL.md # Primary skill file (start here)
├── AGENTS.md # This file - contributor guidance
├── README.md # Human documentation
├── CHANGELOG.md # Version history
├── docs/ # Version audit plan
├── scripts/ # Structural checks
└── rules/ # Individual rule files
├── 1-*.md # Reactivity rules
├── 2-*.md # Component rules
├── 3-*.md # Control flow rules
├── 4-*.md # State management rules
├── 5-*.md # Refs & DOM rules
├── 6-*.md # Performance rules
├── 7-*.md # Accessibility rules
├── 8-*.md # Testing rules
└── 9-*.md # Web component integration rules
Rule Categories
- Category 1: Reactivity
- Category 2: Components
- Category 3: Control Flow
- Category 4: State Management
- Category 5: Refs & DOM
- Category 6: Performance
- Category 7: Accessibility
- Category 8: Testing
- Category 9: Web Component Integration
Rule File Naming
Files follow the pattern [category]-[number]-[hyphenated-topic].md.
Rule File Structure
Each rule file should contain:
- YAML frontmatter with title, category, priority, and
version_basis; add a description when useful. - Problem section explaining what goes wrong.
- Incorrect code examples.
- Correct code examples.
- Why-it-matters guidance.
- Related rules with cross-references.
Examples should stay generic and publishable. Use hypothetical <wc-*> custom elements or native
platform elements, not project-local components.
version_basis lists Solid majors that informed the rule. The current examples came from 1.x work.
Defer the Solid 2.x audit until an official release is available.
Do not mark a rule as based on 2.x merely because its principle appears version-neutral; check the
example's imports, JSX syntax, and runtime behavior against the targeted 2.x release first. Keep
existing rule IDs and links stable when adding version-specific guidance.
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.
- 18d ago Changed · +13 lines · +159 tokens per session b706906138ec
- 2mo ago First seen · 55 lines · 460 tokens per session scan A 523aec908eae
solid-js-best-practices AGENTS.md is an instructions file published in the GitHub repository richardcarls/solid-js-best-practices (2 stars, last pushed 14d ago), licensed MIT. It adds 619 tokens to every session, about $0.0025 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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.