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/testivai/testivai-oss/agents-mdgit clone --depth 1 https://github.com/testivai/testivai-ossWrote 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/testivai/testivai-oss/agents-md)<a href="https://agentmods.dev/instructions/testivai/testivai-oss/agents-md"><img src="https://agentmods.dev/badge/instructions/testivai/testivai-oss/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.02176 | $0.02176 |
| Opus 5 | $0.01088 | $0.01088 |
| Sonnet 5 | $0.00435 | $0.00435 |
| Haiku 4.5 | $0.00218 | $0.00218 |
Grade A, and why
testivai-oss 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 4d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
testivai-oss — Agent Guide
Universal guide for AI coding assistants (Claude Code, Cursor, GitHub Copilot, Gemini, etc.) working inside this repository.
For Claude Code specifically, see CLAUDE.md.
For task recipes, see SKILLS.md.
What this repo is
The public open-source home for the TestivAI visual regression SDKs. Everything here runs fully locally — no account, no API key, no server.
Hard rules — never violate these
-
pnpm only. Never run
npm installoryarnin the workspace root or any package. The only exception is insideaction/(the GitHub Action), which uses plainnpm. -
Local-first, OSS-only. There is no hosted service. Never reference a cloud product, dashboard, account, or API key in docs or code. AI explanation is bring-your-own-model via
@testivai/mcp(explain_snapshot). Core vocabulary: pixel diff, DOM diff, noise hint, layered analysis, baselines, threshold. -
action/dist/index.jsmust always be committed. After any change toaction/src/, rebuild withcd action && npm run buildand commit the updateddist/index.js. CI enforces this. -
Every public API change needs a changeset. Run
pnpm changesetand commit the generated.changeset/*.mdfile with your PR. -
Do not push tags manually without understanding the action versioning scheme. Semver tags (
v1.x.y) roll thev1major tag automatically via CI. See the "Action versioning" section below.
Repo layout
packages/
witness/ @testivai/witness core SDK: CLI, diff engine, baselines, HTML report
playwright/ @testivai/witness-playwright Playwright reporter + capture adapter
webdriverio/ @testivai/witness-webdriverio WebdriverIO service + capture
selenium/ @testivai/witness-selenium Selenium adapter
mcp/ @testivai/mcp MCP server: results + diff images for AI agents
action/ testivai/testivai-oss@v1 GitHub Action: post PR comment + commit status
approve/ testivai/testivai-oss/approve@v1 GitHub Action: /testivai approve command handler
examples/ minimal working examples per framework
docs/ public Markdown documentation
e2e/ OSS smoke E2E test suite
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.
- 4d ago First seen · 243 lines · 2,176 tokens per session scan A eeb8a9cf5ec4
testivai-oss AGENTS.md is an instructions file published in the GitHub repository testivai/testivai-oss (3 stars, last pushed 5d ago), licensed MIT. It adds 2,176 tokens to every session, about $0.0109 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
gh-watch CLAUDE.md
Claude Code instructions for justincampbell/gh-watch, covering gh-watch, architecture, key design decisions, development and testing.
bellwether CLAUDE.md
Claude Code instructions for roderik/bellwether, covering claude.md, what is this?, commands, testing and code style.
invigil AGENTS.md
AGENTS.md instructions for invigil/invigil, covering agents.md — conventions for ai coding agents, build / test / lint and layout.
std-env AGENTS.md
AGENTS.md instructions for unjs/std-env, covering agents, project overview, maintenance, scripts and source structure.
ConsultMe CLAUDE.md
Claude Code instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
ai-research-arm CLAUDE.md
Claude Code instructions for guzus/ai-research-arm, covering claude.md, project overview, core pipeline architecture, key components and scripts (scripts/).