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/file-organizationgit clone --depth 1 https://github.com/iress/design-systemWrote 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.
[](https://agentmods.dev/instructions/iress/design-system/file-organization)<a href="https://agentmods.dev/instructions/iress/design-system/file-organization"><img src="https://agentmods.dev/badge/instructions/iress/design-system/file-organization.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01068 | $0.01068 |
| Opus 5 | $0.00534 | $0.00534 |
| Sonnet 5 | $0.00214 | $0.00214 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
design-system file-organization.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 5d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
File Organization Principles
Implementation Files (.ts/.tsx)
Organize implementation files in this order for better readability and maintainability:
// 1. Imports (external dependencies first, then internal)
import { externalLib } from 'external-package';
import { internalUtil } from '../utils';
// 2. Types and Interfaces (public API)
export interface PublicData {
// Public types that consumers need
}
type InternalType = {
// Internal types for implementation
};
// 3. Constants and Configuration
const CONFIG_VALUE = 'constant';
const REGEX_PATTERN = /pattern/;
// 4. Helper Functions (private implementation details)
const helperFunction = () => {
// Internal utility functions
};
// 5. Main Exported Functions (primary public API)
export const mainFunction = () => {
// Primary public functions
};
Key Principles:
- Public types first - What consumers need to import/use
- Constants grouped together - Configuration and static values
- Helper functions grouped together - Private implementation details
- Main exports last - Primary public API
- Separate concerns - Clear boundaries between public and private code
Test Files (.test.ts/.test.tsx)
Organize test files in this order for clarity and proper setup:
// 1. Imports
import { describe, it, expect, vi } from 'vitest';
import { functionToTest, type TypeToTest } from './moduleToTest';
// 2. Mocks (global setup that affects module loading)
vi.mock('external-dependency', () => ({
// Mock implementation
}));
// 3. Constants and Test Data
const TEST_DATA = {
// Static test data
};
const EXPECTED_VALUES = ['value1', 'value2'];
// 4. Helper Functions (test utilities)
const createTestInstance = () => {
// Test setup helpers
};
const validateStructure = (item: TypeToTest) => {
// Validation helpers
};
// 5. Test Suites (actual test execution)
describe('functionToTest', () => {
// Test cases
});
Key Principles:
- Mocks immediately after imports - They're hoisted anyway and affect module loading
- Constants before helpers - Static configuration before dynamic utilities
- Helper functions before tests - Setup utilities before test execution
- Test suites last - Actual test execution comes after all setup
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.
- 5d ago First seen · 159 lines · 1,068 tokens per session scan A c69e6cb8374c
design-system file-organization.instructions.md is an instructions file published in the GitHub repository iress/design-system (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,068 tokens to every session, about $0.0053 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
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.
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).
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.
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.
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.
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).