agentmods.dev

codingbuddy tests.instructions.md

A set of instructions for reviewing automated tests, covering test structure, behavior, edge cases, errors, and coverage. TDD, or test-driven development, means writing a test before the code that makes it pass.

In plain words
What is it for?
It is for reviewing or designing tests with Arrange-Act-Assert structure, real implementations, edge-case checks, error-path checks, and test-first development for core logic.
Why use it?
It helps reviews look beyond successful examples and check failure cases, boundaries, independence between tests, and important core logic.

Instructions file for GitHub Copilot

31 4mo ago A scan 150 tokens original MIT
View the source file JeremyDev87/codingbuddy
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/jeremydev87/codingbuddy/tests
Clone the repo
git clone --depth 1 https://github.com/JeremyDev87/codingbuddy

Made for: GitHub Copilot.

Per session 150 This file is loaded in full into every session.
When invoked 150 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.00150 $0.00150
Opus 5 $0.00075 $0.00075
Sonnet 5 $0.00030 $0.00030
Haiku 4.5 $0.00015 $0.00015

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

Security

Grade A, and why

codingbuddy 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 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/tests.instructions.md · 26 lines

What it actually says

Test Code Review

Structure

  • Follow Arrange-Act-Assert (AAA) pattern
  • One logical assertion per test
  • Descriptive test names that explain the behavior being tested
  • Group related tests with describe blocks

Quality

  • No mocking — test real behavior with actual implementations
  • Test edge cases: empty inputs, null values, boundary conditions
  • Test error paths, not just happy paths
  • Tests must be independent and not rely on execution order

Coverage

  • Core logic requires test-first TDD (Red → Green → Refactor)
  • UI components allow test-after approach
  • Target 90%+ coverage for core logic
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 · 26 lines · 150 tokens per session scan A 46fc412931cf

Subscribe to this mod's changes

codingbuddy tests.instructions.md is an instructions file published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It adds 150 tokens to every session, about $0.0007 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-30.

Code reviewTestingWriting and docsai-agentsai-codingai-coding-assistantai-rulesclaude-codetypescript
Related

Other instructions, from other repositories

MonkeyCode AGENTS.md

AGENTS.md instructions for chaitin/MonkeyCode, covering git 提交与推送规则, ohmydesign-tmp 例外, 启动 monkeycode debug app（开发与测试）, 1. 编译 agent（必须用最新功能分支代码） and 2. 启动 debug app（ui-next 热加载）.

chaitin/MonkeyCode · 863 tokens

claude-code-plugins AGENTS.md

Instructions for DropFan/claude-code-plugins, covering claude code plugins collection, repository structure, plugin management, development guidelines and adding a self-developed plugin.

DropFan/claude-code-plugins · 794 tokens

codeframe AGENTS.md

AGENTS.md instructions for frankbria/codeframe: The guidelines for this repo live in CLAUDE.md. Read that file.

frankbria/codeframe · 145 tokens

open-mercato CLAUDE.md

Instructions for open-mercato/open-mercato, a project described as: The AI-Engineering Foundation Framework for CRM/ERP and commerce: open-source TypeScript, with multi-tenancy, RBAC, events and domain modules already decided as conventions and specs, so Cursor, Claude Code and Codex build features instead of…

open-mercato/open-mercato · 5 tokens

claude-skills AGENTS.md

AGENTS.md instructions for heymegabyte/claude-skills, covering emdash skills — agent instructions, stack, usage, key files and for ai coding tools.

heymegabyte/claude-skills · 564 tokens

claude-skills copilot-instructions.md

Copilot instructions for heymegabyte/claude-skills, covering emdash skills for github copilot, stack and rules.

heymegabyte/claude-skills · 196 tokens