sceptre-mcp-server: Instructions file for Kiro

.kiro/steering/tdd-workflow.md

sceptre-mcp-server tdd-workflow.md is an instructions file for Kiro from Sceptre/sceptre-mcp-server. It costs 505 tokens per session, scanned A, original, Apache-2.0.

A set of instructions for using test-driven development (TDD) when writing or changing Python code. TDD means writing a failing test first, making it pass with the smallest implementation, then cleaning up the code.

In plain words
What is it for?
Use it when adding features, fixing bugs, or refactoring Python code. It guides interface scaffolding, failing and passing tests, refactoring, and checking test coverage.
Why use it?
It reduces the risk of building the wrong behaviour and helps catch regressions while code is changed. The required test-first cycle also makes the intended interface and edge cases explicit.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Sceptre/sceptre-mcp-server's own configuration. It tells Kiro how to work on sceptre-mcp-server 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 sceptre-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Sceptre/sceptre-mcp-server. 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/Sceptre/sceptre-mcp-server/main/.kiro/steering/tdd-workflow.md
Clone the repo
git clone --depth 1 https://github.com/Sceptre/sceptre-mcp-server

Made for: Kiro.

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 sceptre-mcp-server tdd-workflow.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/tdd-workflow/github.svg)](https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/tdd-workflow)
Your own site
<a href="https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/tdd-workflow"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/tdd-workflow/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 sceptre-mcp-server tdd-workflow.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/tdd-workflow"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/tdd-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 505 This file is loaded in full into every session.
When invoked 505 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00505 $0.00505
Opus 5 $0.00253 $0.00253
Sonnet 5 $0.00101 $0.00101
Haiku 4.5 $0.00051 $0.00051

Measured 4d ago against content hash 0971ac549217, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

sceptre-mcp-server tdd-workflow.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 4d 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.

.kiro/steering/tdd-workflow.md · 74 lines

How it starts

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

TDD Workflow Skill

Activate this skill when implementing new features, fixing bugs, or refactoring Python code.

The Cycle: RED → GREEN → REFACTOR

Step 1: Define the Interface (SCAFFOLD)

  • Define type hints and function signatures
  • Create function/class stubs that raise NotImplementedError
  • Clarify the contract before writing any logic

Step 2: Write Failing Tests (RED)

  • Write tests that describe the desired behavior
  • Cover happy path, edge cases, and error scenarios
  • Run tests — they MUST fail (poetry run pytest -q)

Step 3: Implement Minimal Code (GREEN)

  • Write the simplest code that makes all tests pass
  • Don't optimize yet — just make it work
  • Run tests — they should all pass now

Step 4: Refactor (IMPROVE)

  • Clean up the implementation while keeping tests green
  • Extract constants, improve naming, reduce duplication
  • Run tests after each refactoring step

Step 5: Verify Coverage

  • Check coverage is at 80%+: poetry run pytest --cov --cov-report=term-missing -q
  • Add tests for any uncovered paths
  • Focus on meaningful coverage, not just line count

Test Structure Template

import pytest
from unittest.mock import MagicMock, patch


class TestModuleName:
    """Tests for [Module/Function Name]."""

    def test_happy_path_when_valid_input(self):
        # Arrange
        input_data = {...}
        # Act
        result = function_under_test(input_data)
        # Assert
        assert result == expected

    def test_raises_value_error_on_empty_input(self):
        with pytest.raises(ValueError, match="Input cannot be empty"):
            function_under_test({})

    @pytest.mark.parametrize("input,expected", [
        (None, None),
        ("", ""),
        ("valid", "VALID"),
    ])
    def test_edge_cases(self, input, expected):
        assert function_under_test(input) == expected

Rules

  • NEVER write implementation before tests
  • NEVER modify tests to make them pass (fix the implementation)
  • Each test should test ONE behavior
  • Tests should be independent (no shared mutable state between tests)
  • Mock external dependencies (boto3, opensearch, slack_sdk), not internal logic

Read the full file on GitHub · 74 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. 4d ago First seen · 74 lines · 505 tokens per session scan A 0971ac549217

Subscribe to this mod's changes

sceptre-mcp-server tdd-workflow.md is an instructions file published in the GitHub repository Sceptre/sceptre-mcp-server (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 505 tokens to every session, about $0.0025 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-09-08.

Related

Other instructions, from other repositories

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.

github/spec-kit · 7,126 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,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

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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens