caddis-plugin: Instructions file for GitHub Copilot

.github/instructions/testing.instructions.md

caddis-plugin testing.instructions.md is an instructions file for GitHub Copilot from saajunaid/caddis-plugin. It costs 4,330 tokens per session, scanned A, original, MIT.

A set of testing instructions for applications that use pytest, a Python tool for writing and running automated tests.

In plain words
What is it for?
Use it when writing or reviewing pytest-based tests for an application.
Why use it?
It gives testing work a consistent set of guidelines when using pytest. The description does not provide more detail about the specific rules.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is saajunaid/caddis-plugin's own configuration. It tells GitHub Copilot how to work on caddis-plugin itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything caddis-plugin configures →

Reuse

Borrowing it

Nothing to install: this file belongs to saajunaid/caddis-plugin. 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/saajunaid/caddis-plugin/main/.github/instructions/testing.instructions.md
Clone the repo
git clone --depth 1 https://github.com/saajunaid/caddis-plugin

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.

agentmods badge for caddis-plugin testing.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/saajunaid/caddis-plugin/testing/github.svg)](https://agentmods.dev/instructions/saajunaid/caddis-plugin/testing)
Your own site
<a href="https://agentmods.dev/instructions/saajunaid/caddis-plugin/testing"><img src="https://agentmods.dev/badge/instructions/saajunaid/caddis-plugin/testing/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.

agentmods 80×15 button for caddis-plugin testing.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/saajunaid/caddis-plugin/testing"><img src="https://agentmods.dev/badge/instructions/saajunaid/caddis-plugin/testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,330 This file is loaded in full into every session.
When invoked 4,330 The same file — it is already loaded in full.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04330 $0.04330
Opus 5.5 $0.01732 $0.01732
Sonnet 5.5 $0.00866 $0.00866
Haiku 4.5 $0.00433 $0.00433

Measured 1mo ago against content hash a6292ebbf833, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

caddis-plugin testing.instructions.md scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

response = requests.get("https://api.example.com")
.github/instructions/testing.instructions.md · 756 lines

How it starts

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

Testing Guidelines

Standards for writing tests for Streamlit, FastAPI, and Python applications.

Test Structure

project/
├── src/
│   └── app/
│       ├── services/
│       └── repositories/
└── tests/
    ├── conftest.py          # Shared fixtures
    ├── unit/
    │   ├── test_services.py
    │   └── test_utils.py
    ├── integration/
    │   ├── test_api.py
    │   └── test_database.py
    └── e2e/
        └── test_workflows.py

Naming Conventions

# Test files: test_<module>.py
# test_complaint_service.py

# Test functions: test_<action>_<scenario>_<expected_outcome>
def test_create_complaint_with_valid_data_returns_complaint_id():
    ...

def test_create_complaint_with_missing_description_raises_validation_error():
    ...

# Test classes: Test<ClassName>
class TestComplaintService:
    def test_create_returns_id(self):
        ...

Fixtures

conftest.py

# tests/conftest.py
import pytest
from unittest.mock import MagicMock, AsyncMock
from datetime import datetime
from uuid import uuid4

from app.models.complaint import Complaint, ComplaintCreate

@pytest.fixture
def sample_complaint() -> Complaint:
    """Create a sample complaint for testing."""
    return Complaint(
        id=uuid4(),
        customer_id="CUST001",
        complaint_type="billing",
        description="Test complaint description",
        priority=3,
        status="open",
        created_at=datetime.now()
    )

@pytest.fixture
def sample_complaint_create() -> ComplaintCreate:
    """Create sample complaint creation data."""
    return ComplaintCreate(
        customer_id="CUST001",
        complaint_type="billing",
        description="Test complaint description for creation",
        priority=3
    )

@pytest.fixture
def mock_db_adapter():
    """Create a mock database adapter."""
    adapter = MagicMock()
    adapter.fetch_dataframe = MagicMock(return_value=pd.DataFrame())
    adapter.execute = MagicMock(return_value=True)
    return adapter

@pytest.fixture
def mock_async_db():
    """Create a mock async database adapter."""
    adapter = AsyncMock()
    adapter.fetch = AsyncMock(return_value=[])
    adapter.execute = AsyncMock(return_value=True)
    return adapter

Read the full file on GitHub · 756 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.

  1. 1mo ago First seen · 756 lines · 4,330 tokens per session scan A a6292ebbf833

Subscribe to this mod's changes

caddis-plugin testing.instructions.md is an instructions file published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 4,330 tokens to every session, about $0.0173 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

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 · 9,715 tokens

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,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens