mcpkernel testing-guidelines.instructions.md

Instructions for writing and changing MCPKernel tests with pytest, a Python testing framework, including asynchronous tests and shared test fixtures.

In plain words
What is it for?
Use them when adding or updating tests: organize test files and names, test async code, mock outside services, and run all or selected pytest tests.
Why use it?
They provide consistent test structure and help prevent tests from depending on live external services or breaking existing behavior.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/piyushptiwari1/mcpkernel/testing-guidelines
Clone the repo
git clone --depth 1 https://github.com/piyushptiwari1/mcpkernel

Made for: GitHub Copilot.

Per session 330 This file is loaded in full into every session.
When invoked 330 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00330 $0.00330
Opus 5 $0.00165 $0.00165
Sonnet 5 $0.00066 $0.00066
Haiku 4.5 $0.00033 $0.00033

Measured yesterday against content hash ceed84e6988c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcpkernel testing-guidelines.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 yesterday.

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/testing-guidelines.instructions.md · 56 lines

What it actually says

MCPKernel Testing Guidelines

Framework

  • pytest with pytest-asyncio for async tests
  • Mark async tests: @pytest.mark.asyncio
  • Shared fixtures in tests/conftest.py

Test Structure

class TestFeatureName:
    """Tests for feature_name."""
    
    def test_expected_behavior(self):
        """Test that X does Y when Z."""
        # Arrange
        ...
        # Act
        result = function_under_test(...)
        # Assert
        assert result == expected
    
    @pytest.mark.asyncio
    async def test_async_behavior(self):
        """Test async operation."""
        result = await async_function(...)
        assert result is not None

Naming

  • Files: test_<module>.py
  • Classes: TestClassName
  • Functions: test_<behavior>_<condition>

Commands

# All tests
python -m pytest tests/ -v --tb=short

# Single file
python -m pytest tests/test_proxy.py -v

# Single test
python -m pytest tests/test_proxy.py::TestProxy::test_name -v

Rules

  • Tests must not depend on external services
  • Use mocks for I/O — unittest.mock.AsyncMock for async
  • Each test must be independent and idempotent
  • Target: all 106+ existing tests must continue to pass
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. yesterday First seen · 56 lines · 330 tokens per session scan A ceed84e6988c

Subscribe to this mod's changes

mcpkernel testing-guidelines.instructions.md is an instructions file published in the GitHub repository piyushptiwari1/mcpkernel (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 330 tokens to every session, about $0.0016 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.