Use it to document unit, integration, system, acceptance, performance, and security tests, including steps, expected results, traceability, and defects.

It gives a structured way to plan, run, and record tests, while linking results and defects back to requirements.

How zarfld/presonus-studiolive-mcp configures GitHub Copilot

Q: What is presonus-studiolive-mcp phase-07-verification-validation.instructions.md?

Software testing guidance based on IEEE 1012, a standard for checking whether software meets its requirements and users’ needs.

Reuse

Borrowing it

Nothing to install: this file belongs to zarfld/presonus-studiolive-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/instructions/phase-07-verification-validation.instructions.md

Clone the repo

git clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcp

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation/github.svg)](https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation)

Your own site

<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/phase-07-verification-validation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9,478 This file is loaded in full into every session.

When invoked 9,478 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original 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.

Model	Per session	Once invoked
Fable 5.1	$0.09478	$0.09478
Opus 5	$0.04739	$0.04739
Sonnet 5	$0.01896	$0.01896
Haiku 4.5	$0.00948	$0.00948

Measured 9d ago against content hash 98edf25b5ef7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

presonus-studiolive-mcp phase-07-verification-validation.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 9d 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/phase-07-verification-validation.instructions.md · 1,159 lines

How it starts

The opening of the file, as written. The whole thing — 1,159 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Phase 07: Verification & Validation (V&V)

Standards: IEEE 1012-2016 (System, Software, and Hardware Verification and Validation)
XP Integration: Acceptance Testing, Customer Tests, Test-Driven Development

🎯 Phase Objectives

Verify software against requirements and design
Validate that software meets stakeholder needs
Execute comprehensive test plans
Ensure requirements traceability
Perform acceptance testing with customer
Document test results and defects
Report test results with courage and honesty - See Critical Self-Reflection Guide

📋 Test Case Documentation Approach

⭐ PRIMARY: GitHub Issues (Recommended)

Test cases should be captured as GitHub Issues using the Test Case (TEST) template.

Creating Test Cases as GitHub Issues

Navigate to Issues → New Issue
Select Template: "Test Case (TEST)"
Complete Required Fields:
- Title: Test case description (e.g., "Verify user can login with valid credentials")
- Verified Requirements: Link to requirements using #N syntax
- Test Type: Unit / Integration / System / Acceptance / Performance / Security
- Test Steps: Detailed procedure
- Expected Results: What should happen
- Test Data: Required data/fixtures
- Priority: Critical / High / Medium / Low
Apply Labels: test-case, phase-07, verify-test
Submit → Issue assigned (e.g., #120)

Example TEST Issue:

Title: TEST-AUTH-LOGIN-001: Verify user authentication with valid credentials

Verified Requirements:

Verifies:
- #45 (REQ-F-AUTH-001: User Login)
- #46 (REQ-NF-SECU-002: Session Security)

Test Type: Integration

Test Steps:

1. Navigate to login page
2. Enter valid email: [email protected]
3. Enter valid password: SecurePass123!
4. Click "Login" button
5. Observe redirect and token generation

Expected Results:

- User is authenticated successfully
- Access token and refresh token are generated
- User is redirected to dashboard
- Session is created with 15-minute expiry
- Tokens are stored securely (httpOnly cookie)

Read the full file on GitHub · 1,159 lines

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.

9d ago First seen · 1,159 lines · 9,478 tokens per session scan A 98edf25b5ef7

Subscribe to this mod's changes

presonus-studiolive-mcp phase-07-verification-validation.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 9,478 tokens to every session, about $0.0474 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.

Testing

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

presonus-studiolive-mcp: Instructions file for GitHub Copilot