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.
npx agentmods add instructions/iress/design-system/testing-single-filesgit clone --depth 1 https://github.com/iress/design-systemWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00533 | $0.00533 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
design-system testing-single-files.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.
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running Single Tests with Yarn Workspaces
🎯 Direct Yarn Workspace Commands (Recommended):
# Run a specific test file using --testFile flag
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile MyComponent.test.tsx
# Run any project with a specific file
yarn workspace <package-name> run test:coverage -- --testFile <filename>
🔧 Additional Test Command Options:
# Method 1: Using --testFile flag
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile MyComponent.test.tsx
# Method 2: Using positional argument (regex pattern)
yarn workspace @iress-oss/ids-components run test:coverage -- MyComponent.test.tsx
# Method 3: Using partial filename matching
yarn workspace @iress-oss/ids-components run test:coverage -- MyComponent
📂 File Structure Requirements:
Test files must be in the project's src/ directory:
- ✅
packages/components/src/MyComponent.test.tsx - ❌
packages/components/MyComponent.test.tsx(wrong location)
🚀 Real Examples:
# Test our example files
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile test-file-2.test.ts
# Or using the shortcuts
yarn test:components:file test-file-2.test.ts
💡 Pro Tips:
- Regex matching:
yarn workspace @iress-oss/ids-components run test -- Buttonwill matchButton.test.tsx,ButtonGroup.test.tsx, etc. - Watch mode: Add
--watchto any command for continuous testing - UI mode: Add
--uito any command for the Vitest UI - Coverage: Tests run with coverage by default in this project
🔥 Most Common Usage:
# Quick test of a specific component
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile Button.test.tsx
# Watch mode while developing
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile Button.test.tsx --watch
# UI mode for debugging
yarn workspace @iress-oss/ids-components run test:coverage -- --testFile Button.test.tsx --ui
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.
- 2d ago First seen · 62 lines · 533 tokens per session scan A cf34aea4d357
design-system testing-single-files.instructions.md is an instructions file published in the GitHub repository iress/design-system (1 stars, last pushed 7d ago), licensed Apache-2.0. It adds 533 tokens to every session, about $0.0027 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.
Other instructions, from other repositories
presidio recognizers.instructions.md
Instructions for data-privacy-stack/presidio, covering recognizer changes, the load-bearing rule: test the configuration path, placement and naming, pattern scores and context words.
omnigent copilot-instructions.md
Copilot instructions for omnigent-ai/omnigent, covering copilot code review instructions, e2e test requirement, backend test coverage and frontend test coverage.
Math-To-Manim tests.instructions.md
Guidelines for writing and maintaining tests in Math-To-Manim.
technocore-chat AGENTS.md
Instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
llm-ide-rules pytest-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.
plan-forge testing.instructions.md
Testing rules for Plan Forge — vitest patterns, fake-timers vs tolerance, mocking conventions, and how to read test output without hallucinating failures. Auto-loads when editing test files.