clare tests.instructions.md

Testing guidance for Clare, an AI-assisted development project. It defines tests as checks for rules that must always hold and includes a quick reference for property-based testing, where many generated inputs are tested automatically.

In plain words
What is it for?
Writing JavaScript or Python tests, naming tests around guaranteed rules, adding fast-check or Hypothesis tests, and checking architecture constraints in CI.
Why use it?
It helps prevent tests from merely repeating the current implementation and encourages checks for important limits and structure.

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/jketreno/clare/tests
Clone the repo
git clone --depth 1 https://github.com/jketreno/clare

Made for: GitHub Copilot.

Per session 747 This file is loaded in full into every session.
When invoked 747 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.00747 $0.00747
Opus 5 $0.00374 $0.00374
Sonnet 5 $0.00149 $0.00149
Haiku 4.5 $0.00075 $0.00075

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

Security

Grade A, and why

clare 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 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/tests.instructions.md · 95 lines

How it starts

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

Testing Standards (CLARE — Assertive)

CLARE requires constraint tests, not confirmation tests. Every test file must enforce invariants — things that must always be true — not just describe what the current implementation does.

The Core Distinction

// ❌ Confirmation test — describes implementation, not invariant
it('returns the user', () => {
  const user = getUser(1);
  expect(user.id).toBe(1);
});

// ✅ Constraint test — enforces an invariant
it('always returns a user matching the requested ID', () => {
  fc.assert(
    fc.property(fc.integer({ min: 1, max: 10000 }), (id) => {
      seedUser(id);
      const user = getUser(id);
      expect(user.id).toBe(id);
    })
  );
});

Rules for Every Test File

  1. Name tests as invariants, not as implementations:

    • 'creates a user'
    • 'never allows duplicate emails'
  2. Add at least one property-based test per critical module using fast-check (JS) or hypothesis (Python)

  3. Architecture tests go in tests/architecture/ and run in verify-ci.sh; they must check structural constraints, not behavior:

    // Architecture test example
    test('all API endpoints have rate limiting', () => {
      const endpoints = loadEndpoints();
      endpoints.forEach(ep => expect(ep).toHaveRateLimiting());
    });
    
  4. Schema-lock tests: For any external contract (API, event schema, proto), add a test that would fail if the schema changes unexpectedly:

    test('User API response matches expected schema', () => {
      const response = getUser(seed.userId);
      expect(response).toMatchSnapshot(); // or use Zod schema assertion
    });
    
  5. Test the test — After writing tests, delete the implementation and regenerate it with AI. If tests fail, they are working. If they pass, verify the constraints are strong enough.

Property-Based Testing Quick Reference

// fast-check (TypeScript/JavaScript)
import fc from 'fast-check';

test('never creates negative balances', () => {
  fc.assert(
    fc.property(
      fc.integer({ min: 1, max: 10000 }),
      fc.integer({ min: 1, max: 10000 }),
      (initialBalance, deductAmount) => {
        fc.pre(deductAmount <= initialBalance); // precondition
        const result = deduct(initialBalance, deductAmount);
        expect(result).toBeGreaterThanOrEqual(0);
      }
    )
  );
});

Read the full file on GitHub · 95 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 · 95 lines · 747 tokens per session scan A 441a7298b310

Subscribe to this mod's changes

clare tests.instructions.md is an instructions file published in the GitHub repository jketreno/clare (5 stars, last pushed 1mo ago), licensed MIT. It adds 747 tokens to every session, about $0.0037 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.

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,104 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,182 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,345 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

next.js 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