Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginnpx agentmods add skills/navraj007in/architecture-cowork-plugin/testing-strategyWrote 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/skills/navraj007in/architecture-cowork-plugin/testing-strategy)<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/testing-strategy"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/testing-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/navraj007in/architecture-cowork-plugin/testing-strategy"><img src="https://agentmods.dev/badge/skills/navraj007in/architecture-cowork-plugin/testing-strategy.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.02772 |
| Opus 5 | $0.00010 | $0.01386 |
| Sonnet 5 | $0.00004 | $0.00554 |
| Haiku 4.5 | $0.00002 | $0.00277 |
Grade A, and why
testing-strategy 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 8d 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy Skill
Covers unit, integration, and e2e test patterns for all supported frameworks.
Test File Organization
Folder Structure
- Unit tests: co-locate with source files
src/services/user.ts→src/services/__tests__/user.test.ts(Jest/Vitest)src/services/user.ts→src/services/test_user.py(pytest)
- Integration tests: separate
tests/directory at project roottests/integration/auth.test.tstests/integration/database.test.ts
- E2E tests: separate
e2e/ortests/e2e/directorye2e/flows/login.test.tse2e/flows/checkout.test.ts
File Naming Convention
- Unit:
<module>.test.tsor<module>_test.py - Integration:
<feature>.integration.test.tsortest_<feature>.py - E2E:
<flow>.e2e.test.tsortest_<flow>_e2e.py
Test Structure: Arrange-Act-Assert
All tests MUST follow AAA pattern:
describe('UserService', () => {
describe('createUser', () => {
it('should create a user with valid email and name', () => {
// ARRANGE: Setup test data, mocks, fixtures
const email = '[email protected]';
const name = 'Alice Chen';
// ACT: Call the function under test
const user = service.createUser(email, name);
// ASSERT: Verify the result
expect(user.email).toBe(email);
expect(user.name).toBe(name);
expect(user.id).toBeDefined();
});
});
});
Golden rule: One logical assertion per test (one reason to fail).
Test Naming: Descriptive, Not Clever
❌ BAD:
it('works', () => { ... });
it('user creation 1', () => { ... });
✅ GOOD:
it('should create a user with valid email and return user object with id', () => { ... });
it('should reject email without @ symbol', () => { ... });
it('should hash password before storing in database', () => { ... });
Pattern: should [what happens] [given conditions if not obvious]
Framework-Specific Setup
Node.js / TypeScript (Jest / Vitest)
// jest.config.js
module.exports = {
preset: 'ts-jest',
testEnvironment: 'node',
roots: ['<rootDir>/src', '<rootDir>/tests'],
testMatch: ['**/__tests__/**/*.ts', '**/*.test.ts'],
collectCoverageFrom: [
'src/**/*.ts',
'!src/**/*.d.ts',
'!src/index.ts'
],
coverageThreshold: {
global: {
branches: 80,
functions: 80,
lines: 80,
statements: 80
}
}
};
// tsconfig.test.json
{
"extends": "./tsconfig.json",
"compilerOptions": {
"jsx": "react",
"types": ["jest", "node"]
}
}
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.
- 8d ago First seen · 444 lines · 19 tokens per session scan A 3d2b84bbefc5
testing-strategy is a skill published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 2,772 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
test-implement
Implements React/TypeScript unit, integration, and browser E2E tests with the repository's configured runner, mocks, setup, and browser harness. Use when creating or completing frontend tests and generated test skeletons.
testing-assistant
Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.
verify
Verification loop — lint -> typecheck -> unit -> integration -> e2e.
check-coverage
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
mandu-testing
Testing patterns for Mandu applications. Use when writing unit tests, integration tests, or E2E tests. Triggers on test, spec, Bun test, Playwright, or testing tasks.