Borrowing it
Nothing to install: this file belongs to cacr92/WeReply. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cacr92/WeReply/main/.claude/skills/testing-strategy/SKILL.mdgit clone --depth 1 https://github.com/cacr92/WeReplyWrote 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/cacr92/wereply/testing-strategy)<a href="https://agentmods.dev/skills/cacr92/wereply/testing-strategy"><img src="https://agentmods.dev/badge/skills/cacr92/wereply/testing-strategy.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.00088 | $0.03226 |
| Opus 5 | $0.00044 | $0.01613 |
| Sonnet 5 | $0.00018 | $0.00645 |
| Haiku 4.5 | $0.00009 | $0.00323 |
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 7d 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 — 545 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy Skill
Comprehensive testing guidance for Tauri applications with Rust backend and React frontend.
Overview
This skill provides testing strategies for:
- Rust unit and integration tests
- React component and hook tests
- Tauri command mocking
- Database testing with fixtures
- Test coverage and quality gates
- TDD (Test-Driven Development) workflows
When This Skill Applies
This skill activates when:
- Writing new tests for Rust or TypeScript code
- Implementing test doubles and mocks
- Setting up test infrastructure
- Debugging test failures
- Improving test coverage
- Planning testing strategy for features
Rust Testing
Unit Tests
Location: In the same module as the code being tested
#[cfg(test)]
mod tests {
use super::*;
#[test]
fn test_formula_cost_calculation() {
let materials = vec![
FormulaMaterial {
material_code: "corn".to_string(),
proportion: 50.0,
price: 2.5,
},
FormulaMaterial {
material_code: "soybean".to_string(),
proportion: 50.0,
price: 3.0,
},
];
let cost = calculate_total_cost(&materials);
assert!((cost - 2.75).abs() < 0.01); // Average of 2.5 and 3.0
}
#[test]
fn test_empty_materials() {
let materials = vec![];
let cost = calculate_total_cost(&materials);
assert_eq!(cost, 0.0);
}
#[test]
#[should_panic(expected = "Proportion cannot be negative")]
fn test_negative_proportion_panics() {
let material = FormulaMaterial {
material_code: "test".to_string(),
proportion: -10.0,
price: 1.0,
};
validate_material(&material);
}
}
Integration Tests
Location: tests/ directory at project root
// tests/formula_integration_tests.rs
use ca_cr_feed_formula::database::create_pool;
use ca_cr_feed_formula::formula::FormulaService;
#[tokio::test]
async fn test_create_and_retrieve_formula() {
// Use test database
let pool = create_pool(":memory:").await.expect("Failed to create pool");
let service = FormulaService::new(pool);
// Create formula
let create_dto = CreateFormulaDto {
name: "Test Formula".to_string(),
species_code: "pig".to_string(),
description: None,
};
let formula_id = service.create_formula(create_dto)
.await
.expect("Failed to create formula");
// Retrieve formula
let formula = service.get_formula(formula_id)
.await
.expect("Failed to retrieve formula");
assert_eq!(formula.name, "Test Formula");
assert_eq!(formula.species_code, "pig");
}
#[tokio::test]
async fn test_formula_not_found() {
let pool = create_pool(":memory:").await.expect("Failed to create pool");
let service = FormulaService::new(pool);
let result = service.get_formula(99999).await;
assert!(result.is_err());
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 545 lines · 88 tokens per session scan A 1b6f6211cb71
testing-strategy is a skill published in the GitHub repository cacr92/WeReply (6 stars, last pushed 7mo ago), licensed MIT. It adds 88 tokens to every session and 3,226 once invoked, about $0.0004 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
write-vibe-tests
Write or refactor Mistral Vibe tests with proper decoupling. Use when adding behavior coverage, testing ports/adapters, replacing brittle mocks, creating fakes, adding characterization tests before refactors, or changing tests under tests/ for vibe/core, vibe/cli, vibe/acp, tools, config, sessions, skills, hooks, MCP…
composing-matchers
Build compound Gomega assertions by combining matchers — And/SatisfyAll (all pass), Or/SatisfyAny (any pass), Not (negate), WithTransform to map the actual before matching, Satisfy for an ad-hoc predicate, HaveValue to dereference pointers/interfaces, HaveField for struct fields and method results, HaveEach for every…
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
nw-fp-fsharp
F# language-specific patterns, Railway-Oriented Programming, and Computation Expressions.
nw-fp-kotlin
Kotlin language-specific patterns with Arrow, Raise DSL, and coroutine-based effects.
nw-hexagonal-testing
5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples.