mcp-server-milvus python-calisthenics.instructions.md

A set of Python coding rules based on Object Calisthenics, a style of keeping object-oriented code small and structured. It mainly applies to business-domain classes such as entities and value objects.

In plain words
What is it for?
Reviewing or writing Python business logic while following the nine Object Calisthenics rules, such as limiting indentation within methods.
Why use it?
It helps prevent deeply nested and hard-to-maintain business logic. It also makes clear which kinds of code the rules do and do not cover.

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/danchev/mcp-server-milvus/python-calisthenics
Clone the repo
git clone --depth 1 https://github.com/danchev/mcp-server-milvus

Made for: GitHub Copilot.

Per session 1,704 This file is loaded in full into every session.
When invoked 1,704 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin fork From a forked repository.
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.01704 $0.01704
Opus 5 $0.00852 $0.00852
Sonnet 5 $0.00341 $0.00341
Haiku 4.5 $0.00170 $0.00170

Measured 2d ago against content hash 0e319bc80b21, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-server-milvus python-calisthenics.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 2d 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/python-calisthenics.instructions.md · 263 lines

How it starts

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

Object Calisthenics Rules for Python

⚠️ Warning: This file contains the 9 original Object Calisthenics rules. No additional rules must be added, and none of these rules should be replaced or removed. Examples may be added later if needed.

Objective

This rule enforces the principles of Object Calisthenics to ensure clean, maintainable, and robust code in Python, primarily for business domain code.

Scope and Application

  • Primary focus: Business domain classes (aggregates, entities, value objects, domain services)
  • Secondary focus: Application layer services and use case handlers
  • Exemptions:
    • DTOs (Data Transfer Objects)
    • API models/contracts
    • Configuration classes
    • Simple data containers without business logic
    • Infrastructure code where flexibility is needed

Key Principles

1. One Level of Indentation per Method:

  • Keep methods simple and limit the level of indentation to one.
# Bad Example - multiple levels of indentation
def send_newsletter():
    for user in users:
        if user.is_active:
            # Do something
            mailer.send(user.email)

# Good Example - Extracted method to reduce indentation
def send_newsletter():
    for user in users:
        send_email(user)

def send_email(user):
    if user.is_active:
        mailer.send(user.email)

2. Don't Use the ELSE Keyword:

  • Avoid using else to simplify control flow. Use early returns or fail fast.
# Bad Example - Using else
def process_order(order):
    if order.is_valid:
        # Process order
    else:
        # Handle invalid order

# Good Example - Avoiding else
def process_order(order):
    if not order.is_valid:
        return  # early return to handle invalid case
    # Process order
  • Fail Fast principle example:
def process_order(order):
    if order is None:
        raise ValueError("Order cannot be None")
    if not order.is_valid:
        raise ValueError("Invalid order")
    # Process order

Read the full file on GitHub · 263 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. 2d ago First seen · 263 lines · 1,704 tokens per session scan A 0e319bc80b21

Subscribe to this mod's changes

mcp-server-milvus python-calisthenics.instructions.md is an instructions file published in the GitHub repository danchev/mcp-server-milvus (1 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 1,704 tokens to every session, about $0.0085 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.