Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/richardcarls/solid-js-best-practices/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.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 | $0.00460 | $0.00460 |
| Opus 5 | $0.00230 | $0.00230 |
| Sonnet 5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
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 4d 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.
What it actually says
Solid.js Best Practices - Contributor Guide
For AI agents: The primary skill content is in SKILL.md, which includes the rule index, task-based rule selection, common mistakes, and React comparison tables.
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
└── 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 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.
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.
- 4d 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 1mo ago), licensed MIT. It adds 460 tokens to every session, about $0.0023 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
turbo CLAUDE.md
Claude Code instructions for tobihagemann/turbo, covering turbo, project structure and key files.
Codex-Skills AGENTS.md
AGENTS.md instructions for TheGoat395/Codex-Skills, covering repository operating notes, required checks, evidence rules and change hygiene.
ai-proxy CLAUDE.md
Instructions for mrhuangyong/ai-proxy, covering claude.md, project overview, build & dev commands, architecture and dual server pattern.
supergraph AGENTS.md
Instructions for datit309/supergraph, covering supergraph — mandatory workflows, skills, auto language detection, tiered workflow — pick the right tier first and full pipeline (tier 3).
give-me-job AGENTS.md
Instructions for kyoungbinkim/give-me-job, covering give-me-job repository instructions, default workflow, skill routing, working on this repository and development loop.
agent-website-design-skills AGENTS.md
Instructions for divyanshu-iitian/agent-website-design-skills, covering agent instructions, repository goal, how to use, skill selection and constraints.