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/elanmed/agent-js/agents-mdgit clone --depth 1 https://github.com/elanmed/agent-jsWrote 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/elanmed/agent-js/agents-md)<a href="https://agentmods.dev/instructions/elanmed/agent-js/agents-md"><img src="https://agentmods.dev/badge/instructions/elanmed/agent-js/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.00764 | $0.00764 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
agent-js 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-js
You are running in a container. Make all changes to /agent-js at the root of the filesystem.
This is a Node.js project. Only Node.js APIs should be used. Use node for running and testing, and pnpm as the package manager.
Development
After every change, run linting, types, tests, and formatting:
pnpm run lint
pnpm run types
pnpm run test
pnpm run format
Or all at once:
pnpm run ci
Guidelines
- Never add comments
- Minimize diffs — only change what's necessary
- All changes must have test coverage
- Prefer
assert.deepStrictEqualover multiple individual field assertions — check the whole object in one call - Never use
content: result.contentin deepStrictEqual assertions — it's a tautology. Inline the actual expected value - Never use
assert.ok(result.includes(...))— assert on the whole string withassert.equalorassert.strictEqual - Only use
===and!==; never use==,!=, or truthy/falsy coercions likeif (obj)orif (!obj). Use!only on boolean expressions - For string assertions with newlines: use template literals when the string contains any newline that is not a single trailing one. If it's just a single trailing newline, use
"...\n"instead - For fs, import
fsDepsdirectly fromdeps.ts. In tests, usesetupFakeDeps()fromtest-helpers.tsto mock all fs methods,processEnv, andprocessStdoutglobally. UsetestFs._files/testFs._dirs/testFs._globResultsto set up fixture state. ImporttestFsandsetupFakeDepsfrom./test-helpers.ts. processEnv.getandprocessStdout.writeare also indeps.tsand mocked bysetupFakeDeps(). UsetestProcessEnv._set(key, value)for env vars. OverrideprocessStdout.writewith an additionalmock.method(processStdout, "write", ...)if you need to capture output.- Pure utility functions do not need deps — import and call them directly in tests.
fs mocking example
Production code:
import { fsDeps } from "./deps.ts";
export function readConfig() {
if (fsDeps.existsSync("config.json") === false) return null;
return JSON.parse(fsDeps.readFileSync("config.json").toString());
}
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.
- 3d ago First seen · 86 lines · 764 tokens per session scan A d439e06c0124
agent-js AGENTS.md is an instructions file published in the GitHub repository elanmed/agent-js (2 stars, last pushed 3d ago), licensed MIT. It adds 764 tokens to every session, about $0.0038 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.