Borrowing it
Nothing to install: this file belongs to loveautomate/ai-qa-agent. 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/loveautomate/ai-qa-agent/main/AGENTS.mdgit clone --depth 1 https://github.com/loveautomate/ai-qa-agentWrote 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/loveautomate/ai-qa-agent/agents-md)<a href="https://agentmods.dev/instructions/loveautomate/ai-qa-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/loveautomate/ai-qa-agent/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.1 | $0.00574 | $0.00574 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
ai-qa-agent 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 6d 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 — 26 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI QA Agent (repo hints)
- Architecture & folder map (Mermaid): README.md — Architecture
- Orchestrator rule:
.cursor/rules/orchestrator.mdc(6 phases; VALIDATE always starts withnpm run test:reportfor UI e2e so you review HTML report + traces first; playwright-cli optional after that) - PRD / roadmap:
.agent/docs/prd.md - Workflow skill note:
.agent/skills/qa-workflow.md - VALIDATE — mandatory evidence (UI e2e): Agent runs
npm run test:report(test:clean+ full artifacts + opens HTML report) before validate discussion; you start from the report and trace viewers. Seepackage.jsonandplaywright.config.ts(PW_REPORT_ALL). - VALIDATE — optional debug:
.agent/skills/playwright-cli.md· playwright-cli skills (default path):.claude/skills/playwright-cli/(refresh:npm run playwright-cli:skills)
.agent/ holds skills/ and docs/ only.
Demo base URLs: playwright.config.ts — DEMO_E2E_BASE_URL, DEMO_API_BASE_URL (edit in source when changing targets).
E2E spec naming: tests/e2e/{target}.spec.ts (e.g. saucedemo.spec.ts). Avoid redundant filename tags such as -bdd; express style in test.step / plans, not in the file name.
Evidence: After a run, open the Playwright report with npx playwright show-report, or open playwright-report/index.html. Markdown summaries live under reports/ when generated.
Extending or changing tests: Update tests/plans/*.md and re-run PLAN → DEVELOP → TEST → HEAL → REPORT → VALIDATE until the user is satisfied (orchestrator).
Branching (framework vs demo content)
main: Test framework and agent docs —playwright.config.ts,scripts/,package.jsontest scripts,.agent/,.cursor/rules/,README.md, etc.- Feature branches (e.g.
ui-test,api-test): Demo plans, specs, and Markdown reports for a given exercise may land here without merging those artifacts tomain, somainstays a clean harness. Cherry-pick or merge framework-only commits tomainwhen promoting tooling updates.
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.
- 6d ago First seen · 26 lines · 574 tokens per session scan A 1b775916b753
ai-qa-agent AGENTS.md is an instructions file published in the GitHub repository loveautomate/ai-qa-agent (3 stars, last pushed 4mo ago), licensed MIT. It adds 574 tokens to every session, about $0.0029 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
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.
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.
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).
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).
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.
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.