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 skills add Primadetaautomation/primadata-marketplace --skill testing-fundamentalsgit clone --depth 1 https://github.com/Primadetaautomation/primadata-marketplaceWrote 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/primadetaautomation/primadata-marketplace/testing-fundamentals)<a href="https://agentmods.dev/skills/primadetaautomation/primadata-marketplace/testing-fundamentals"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/testing-fundamentals/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/primadetaautomation/primadata-marketplace/testing-fundamentals"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/testing-fundamentals.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.00021 | $0.02748 |
| Opus 5 | $0.00010 | $0.01374 |
| Sonnet 5 | $0.00004 | $0.00550 |
| Haiku 4.5 | $0.00002 | $0.00275 |
Grade A, and why
testing-fundamentals 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 11d 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Fundamentals Skill
Overview
This skill provides comprehensive testing strategies following TDD principles with 80%+ coverage requirements. It ensures quality assurance through systematic testing approaches.
When to Use This Skill
- Implementing new features (TDD approach)
- Creating comprehensive test suites
- Analyzing test coverage gaps
- Pre-production quality validation
- Refactoring with safety net
TDD Workflow (Level 1 - Always Loaded)
🔴 Red → 🟢 Green → 🔵 Refactor
Step 1: Red - Write Failing Test First
// Write the test BEFORE implementation
describe('UserService', () => {
it('should create a new user with valid data', async () => {
// Arrange
const userData = {
email: '[email protected]',
password: 'SecurePass123!',
name: 'Test User'
};
// Act
const result = await userService.createUser(userData);
// Assert
expect(result).toHaveProperty('id');
expect(result.email).toBe(userData.email);
expect(result.name).toBe(userData.name);
expect(result).not.toHaveProperty('password'); // Password should not be returned
});
});
// Test should FAIL initially (Red)
Step 2: Green - Write Minimal Code to Pass
class UserService {
async createUser(data: CreateUserDto): Promise<User> {
// Minimal implementation to make test pass
const user = {
id: generateId(),
email: data.email,
name: data.name,
// password is hashed and not returned
};
await this.userRepository.save(user);
return user;
}
}
// Test should PASS now (Green)
Step 3: Refactor - Improve Code Quality
class UserService {
async createUser(data: CreateUserDto): Promise<User> {
// Refactor with better structure
this.validateUserData(data);
const hashedPassword = await this.hashPassword(data.password);
const user = User.create({
email: data.email,
name: data.name,
passwordHash: hashedPassword,
});
return this.userRepository.save(user);
}
private validateUserData(data: CreateUserDto): void {
if (!validator.isEmail(data.email)) {
throw new ValidationError('Invalid email');
}
if (data.password.length < 8) {
throw new ValidationError('Password too short');
}
}
private async hashPassword(password: string): Promise<string> {
return bcrypt.hash(password, 12);
}
}
// Tests still PASS after refactoring
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.
- 11d ago First seen · 435 lines · 21 tokens per session scan A 45b402301324
testing-fundamentals is a skill published in the GitHub repository Primadetaautomation/primadata-marketplace (5 stars, last pushed 9mo ago), licensed MIT. It adds 21 tokens to every session and 2,748 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-08-31.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
iterative-development
TDD iteration loops using Claude Code Stop hooks - runs tests after each response, feeds failures back automatically.
python
Python development with ruff, mypy, pytest - TDD and type safety.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.