ndb-core e2e-tests.instructions.md

Project-specific instructions for writing end-to-end tests in Aam-Digital/ndb-core. End-to-end tests check a complete user flow through the application, and Playwright is the tool used for browser testing.

In plain words
What is it for?
It is for creating or maintaining browser tests that exercise complete ndb-core workflows with consistent test data and controlled dates.
Why use it?
It helps tests follow the project's established imports, application-loading process, test-data generators, and date handling.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/aam-digital/ndb-core/e2e-tests
Clone the repo
git clone --depth 1 https://github.com/Aam-Digital/ndb-core

Made for: GitHub Copilot.

Per session 1,738 This file is loaded in full into every session.
When invoked 1,738 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.01738 $0.01738
Opus 5 $0.00869 $0.00869
Sonnet 5 $0.00348 $0.00348
Haiku 4.5 $0.00174 $0.00174

Measured 3d ago against content hash b4123c18c832, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ndb-core e2e-tests.instructions.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.

.github/instructions/e2e-tests.instructions.md · 237 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 237 lines · 1,738 tokens per session scan A b4123c18c832

Subscribe to this mod's changes

ndb-core e2e-tests.instructions.md is an instructions file published in the GitHub repository Aam-Digital/ndb-core (94 stars, last pushed 3d ago), licensed GPL-3.0. It adds 1,738 tokens to every session, about $0.0087 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-30.