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.
curl -O https://raw.githubusercontent.com/zarfld/presonus-studiolive-mcp/master/.github/instructions/tests.instructions.mdgit clone --depth 1 https://github.com/zarfld/presonus-studiolive-mcpWrote 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/zarfld/presonus-studiolive-mcp/tests)<a href="https://agentmods.dev/instructions/zarfld/presonus-studiolive-mcp/tests"><img src="https://agentmods.dev/badge/instructions/zarfld/presonus-studiolive-mcp/tests.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.02915 | $0.02915 |
| Opus 5 | $0.01458 | $0.01458 |
| Sonnet 5 | $0.00583 | $0.00583 |
| Haiku 4.5 | $0.00292 | $0.00292 |
Grade A, and why
presonus-studiolive-mcp 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 5d 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 — 426 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Traceability Requirements
Standards: IEEE 1012-2016 (Verification & Validation), ISO/IEC/IEEE 29148:2018 (Requirements Traceability)
Every Test MUST:
1. Link to Requirement Issue
Include explicit reference to the GitHub issue being verified:
"""
Test user login functionality.
Verifies: #123 (REQ-F-AUTH-001: User Login)
Test Type: Integration
Priority: P0 (Critical)
Acceptance Criteria (from #123):
Given user has valid credentials
When user submits login form
Then user is authenticated and redirected to dashboard
"""
def test_user_login_success():
# Arrange
user = create_test_user(email="[email protected]", password="secure123")
# Act
response = login(email="[email protected]", password="secure123")
# Assert
assert response.status_code == 200
assert response.user.is_authenticated == True
assert response.redirect_url == "/dashboard"
describe('User Login (Verifies #123)', () => {
/**
* Verifies: REQ-F-AUTH-001 (Issue #123)
* Acceptance Criteria: User can log in with valid credentials
* Test Type: Integration
* Priority: P0
*/
it('should authenticate user with valid credentials', async () => {
// Arrange
const user = await createTestUser({
email: '[email protected]',
password: 'secure123'
});
// Act
const response = await login('[email protected]', 'secure123');
// Assert
expect(response.status).toBe(200);
expect(response.user.isAuthenticated).toBe(true);
expect(response.redirectUrl).toBe('/dashboard');
});
});
2. Test Acceptance Criteria
Each test should map to specific acceptance criteria from the requirement issue:
- Copy Given/When/Then scenarios from issue
- Test each scenario separately
- Cover positive and negative cases
- Test boundary conditions
- Test error handling specified in requirement
3. Include Test Metadata
Provide context for test purpose and priority:
# Verifies: #145 (REQ-NF-PERF-002: API Response Time)
# Test Type: Performance
# Priority: P1 (High)
# Threshold: Response time < 200ms for 95th percentile
@pytest.mark.performance
def test_api_response_time():
"""Verify API responds within 200ms for 95% of requests."""
response_times = []
for _ in range(100):
start = time.time()
response = api_client.get('/api/users')
end = time.time()
response_times.append((end - start) * 1000)
p95 = np.percentile(response_times, 95)
assert p95 < 200, f"95th percentile: {p95}ms exceeds 200ms threshold"
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.
- 5d ago First seen · 426 lines · 2,915 tokens per session scan A 2bb2eb58b9f1
presonus-studiolive-mcp tests.instructions.md is an instructions file published in the GitHub repository zarfld/presonus-studiolive-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 2,915 tokens to every session, about $0.0146 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.