js2: Instructions file for Codex

AGENTS.md

js2 AGENTS.md is an instructions file for Codex, OpenCode from loopdive/js2. It costs 754 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for agents working on the loopdive/js2 codebase.

In plain words
What is it for?
It helps prepare for substantial work, write acceptable commit messages, attribute commits correctly, and preserve coding-session context.
Why use it?
It explains the repository's local expectations, so agents can follow its memories, commit style, authorship, and session rules.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions Codex.

This is loopdive/js2's own configuration. It tells Codex and OpenCode how to work on js2 itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything js2 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to loopdive/js2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/loopdive/js2/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/loopdive/js2

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for js2 AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/loopdive/js2/agents-md/github.svg)](https://agentmods.dev/instructions/loopdive/js2/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/loopdive/js2/agents-md"><img src="https://agentmods.dev/badge/instructions/loopdive/js2/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.

agentmods 80×15 button for js2 AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/loopdive/js2/agents-md"><img src="https://agentmods.dev/badge/instructions/loopdive/js2/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 754 This file is loaded in full into every session.
When invoked 754 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00754 $0.00754
Opus 5.5 $0.00302 $0.00302
Sonnet 5.5 $0.00151 $0.00151
Haiku 4.5 $0.00075 $0.00075

Measured 24d ago against content hash e57b977989ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

js2 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 24d 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.

AGENTS.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Claude Memories

  • Before substantial work, review the markdown memories under .claude/memory.
  • Start with MEMORY.md, then read any task-relevant files in the same directory.
  • Treat those memory files as repo-specific operating context, especially around test262 workflow, agent coordination, cleanup rules, and user preferences.

IR-only development policy

  • Development of the old direct-AST compilation path is frozen. Follow the development-freeze policy.
  • Put new language features and semantic fixes in IR or the genuinely shared runtime. Preserve the old path/CI and historical measurements, existing source ownership and holds; shared infrastructure and measurement work remain permitted.
  • An IR flag or IR_FIRST label is not proof of complete IR admission. Keep explicitly selected IR Test262 numbers separate from default/historical results.

Commit Messages

  • Use Claude Code-style commit messages.
  • Write a specific subject line that states the main change clearly.
  • Add a body when the change is non-trivial.
  • In the body, explain what changed and why it changed.
  • Call out behavior changes, important tradeoffs, or follow-up work when relevant.

Preferred shape:

<type>(<scope>): <concise summary>

Explain the main implementation change and the reason for it.

Note behavior changes, risks, or follow-ups if they matter.

Examples of acceptable types: fix, feat, refactor, docs, test, chore.

Commit Attribution

  • Commits produced by an AI agent must be authored by the user: Thomas Tränkler <[email protected]>.
  • Add a co-author trailer identifying the agent that actually produced the commit:
# Codex session
Co-authored-by: Codex <[email protected]>

# Claude session
Co-authored-by: Claude <[email protected]>
  • Never attribute Codex work to Claude or Claude work to Codex.
  • Also add a Model: trailer naming the exact model that produced the commit — vendor, family, version/subtype, and the configured reasoning effort (project-lead order, 2026-08-29; enforced by .husky/commit-msg for any commit carrying an agent co-author trailer):

Read the full file on GitHub · 79 lines

Changes

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.

  1. 24d ago Changed · +10 lines · +112 tokens per session e57b977989ec
  2. 2mo ago Changed · -50 tokens per session 98207a0287a0
  3. 2mo ago First seen · 69 lines · 692 tokens per session scan A 6322e5bb5cf2

Subscribe to this mod's changes

js2 AGENTS.md is an instructions file published in the GitHub repository loopdive/js2 (67 stars, last pushed today), licensed Apache-2.0. It adds 754 tokens to every session, about $0.0030 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-30.

Related

js2 AGENTS.md compared with instructions from other repositories

js2 AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
js2 AGENTS.mdloopdive/js2Instructions file67todayApache-2.0A754Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode