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/lvcoi/solidjskills/agents-mdgit clone --depth 1 https://github.com/lvcoi/solidJSkillsWrote 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/lvcoi/solidjskills/agents-md)<a href="https://agentmods.dev/instructions/lvcoi/solidjskills/agents-md"><img src="https://agentmods.dev/badge/instructions/lvcoi/solidjskills/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.00428 | $0.00428 |
| Opus 5 | $0.00214 | $0.00214 |
| Sonnet 5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
solidJSkills 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 5d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md (SolidJS Repository Standard)
Scope: entire repository.
Repository Intent
Treat this repository as SolidJS-first. Prefer creating or updating SolidJS skills, references, guides, and tooling over generic AI meta-guidance.
Operating Priorities
- Preserve SolidJS reactivity correctness.
- Optimize readability and maintainability before micro-optimization.
- Favor deterministic workflows and checklists in skills.
- Keep
SKILL.mdconcise; move detailed knowledge intoreferences/.
SolidJS Coding and Design Standards
- Prefer fine-grained reactivity primitives intentionally (
createSignal,createMemo,createEffect,createResource,batch,untrack). - Avoid unnecessary effects when derivation is sufficient.
- Keep side effects explicit and isolated.
- Use Solid control flow primitives (
<Show>,<For>,<Switch>,<Match>) for clarity and performance. - Design props and component boundaries to minimize hidden coupling.
- Account for hydration/SSR behavior in guidance and review criteria.
Skill Authoring Standards
When adding or updating a SolidJS skill:
- Use clear trigger language in frontmatter
description(when to use). - Include deterministic workflow steps with acceptance checks.
- Define failure modes and fallback paths.
- Link to only relevant reference files.
- Include output format expectations (checklists, plans, patches, review notes).
- Require citation-backed claims using normalized corpus
doc_idvalues.
Required Review Checklist for SolidJS Artifacts
- Reactivity correctness verified.
- Unnecessary recomputation avoided.
- Control flow primitives chosen appropriately.
- Async and loading states explicit.
- Accessibility and semantic markup considered.
- SSR/hydration concerns addressed where relevant.
- Tests/check commands listed for validation.
- Citations include normalized
doc_idreferences for non-trivial claims.
Scaffolding and Bootstrap Expectations
- Prefer minimal, production-realistic defaults.
- Document package/tooling choices and tradeoffs.
- Provide clear extension points for scaling teams.
- Keep generated structures simple and predictable.
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.
- 5d ago First seen · 53 lines · 428 tokens per session scan A 12a61c39c87a
solidJSkills AGENTS.md is an instructions file published in the GitHub repository lvcoi/solidJSkills (10 stars, last pushed 6mo ago), licensed MIT. It adds 428 tokens to every session, about $0.0021 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
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).
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.
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).