Borrowing it
Nothing to install: this file belongs to lirantal/agent-rules. 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/lirantal/agent-rules/main/.github/instructions/testing.instructions.mdgit clone --depth 1 https://github.com/lirantal/agent-rulesWrote 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/lirantal/agent-rules/testing)<a href="https://agentmods.dev/instructions/lirantal/agent-rules/testing"><img src="https://agentmods.dev/badge/instructions/lirantal/agent-rules/testing/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/lirantal/agent-rules/testing"><img src="https://agentmods.dev/badge/instructions/lirantal/agent-rules/testing.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.06713 | $0.06713 |
| Opus 5.5 | $0.02685 | $0.02685 |
| Sonnet 5.5 | $0.01343 | $0.01343 |
| Haiku 4.5 | $0.00671 | $0.00671 |
Grade A, and why
agent-rules testing.instructions.md scanned grade A with 1 finding 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 1mo 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
To test command-line tools, use `node:child_process` to execute the CLI and assert on its output. For asynchronous operations where you need to capture streamed output or handle more complex interactions, using `exec` wi How it starts
The opening of the file, as written. The whole thing — 715 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Guidelines for Node.js applications
This document outlines the rules and guidelines for AI agents generating test code for modern Node.js applications.
The following are project tests code standards, principles and strategy for for JavaScript and TypeScript projects that you should apply and follow if you are working on a task related to writing tests, updating existing tests, or overall refactoring and making changes to test code.
General Testing Principles
Guiding Principles
- Modern Node.js: All test code must be compatible with Node.js version 22 and above.
- Latest JavaScript: Utilize the latest JavaScript features (ES2022 and beyond), including top-level
awaitand modern syntax. - Built-in Tools: Exclusively use the built-in Node.js test runner (
node:test) and assertion library (node:assert). No third-party testing frameworks (e.g., Jest, Mocha, Chai) should be used. - ES Modules: All code should be written using ES Modules (
import/export). CommonJS (require) should be avoided. - Asynchronous Focus: Tests should be written with an
async-first mindset, effectively handling promises and asynchronous operations. - Clarity and Readability: Tests should be easy to understand. Use descriptive names for
describeblocks andtestcases.
Descriptive Test Naming (Three-Part Structure)
A well-named test clearly communicates its purpose, making test reports more informative and debugging easier for anyone, regardless of their familiarity with the codebase. Adopt a three-part structure for your test names:
- What is being tested? (The unit under test, e.g.,
ProductsService.addNewProduct) - Under what circumstances/scenario? (The specific conditions, e.g.,
no price is passed to the method) - What is the expected result? (The outcome, e.g.,
the new product is not approved)
This structure ensures that a failing test immediately tells you what broke, when it broke, and what the expected behavior was.
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.
- 1mo ago First seen · 715 lines · 6,713 tokens per session scan A b04fff89ddc7
agent-rules testing.instructions.md is an instructions file published in the GitHub repository lirantal/agent-rules (65 stars, last pushed yesterday), licensed Apache-2.0. It adds 6,713 tokens to every session, about $0.0269 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.