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 saeedkolivand/ai-job-hunter-app --skill testing-rulesgit clone --depth 1 https://github.com/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/testing-rules)<a href="https://agentmods.dev/skills/saeedkolivand/ai-job-hunter-app/testing-rules"><img src="https://agentmods.dev/badge/skills/saeedkolivand/ai-job-hunter-app/testing-rules/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/saeedkolivand/ai-job-hunter-app/testing-rules"><img src="https://agentmods.dev/badge/skills/saeedkolivand/ai-job-hunter-app/testing-rules.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.00048 | $0.01561 |
| Opus 5.5 | $0.00019 | $0.00624 |
| Sonnet 5.5 | $0.00010 | $0.00312 |
| Haiku 4.5 | $0.00005 | $0.00156 |
Grade A, and why
testing-rules 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing rules
Frameworks & utilities
- Frontend — Vitest + @testing-library/react, colocated
*.test.ts(x). Reuserenderer/test-support.tsx:createMockClient,renderHookWithClient,exerciseServiceHooks. - Rust —
cargo test; integration insrc-tauri/tests/(incl.cargo test --test architectureboundary guard). - E2E / golden — golden snapshots for PDF/DOCX/template rendering.
When tests are required (testable-logic predicate)
A change requires authoring tests iff a changed .rs/.ts/.tsx file (not test/generated/declaration/config) has a behavioral line change (not pure comment/blank/import/type-decl). Pure deletions don't trigger authoring — instead verify orphaned tests were removed.
Strategy
- Order: integration → unit → e2e. Test behavior, not implementation.
- Coverage of changed code: success + failure + error & security paths (untested error/security path on changed code = HIGH/blocking) + edge cases + validation.
- Prove the guard is real (red-green). A test locking a bugfix must FAIL on the unfixed code and PASS on the fix — confirm it (temporarily revert the fix, or assert the exact sentinel/branch the fix introduced). A regression test that passes both ways guards nothing — a mocked dependency can hide the real failure path.
Mocking
- Allowed: external APIs, AI providers, third-party, expensive ops.
- Never mock internal business logic, ATS scoring, resume generation, or export pipelines — use realistic fixtures.
- Mock fidelity — a stub must reproduce the REAL side-effects of what it replaces. A
vi.fn()standing in for a fn that commits optimistic state (e.g.updateAnswercallingsetAnswersBEFORE its async save) must reproduce that effect (update the controlled prop/state in the test) — otherwise the test passes against logic production would break. A rollback-guard bug shipped green precisely because the mockedupdateAnswernever updated state, so the guard's sentinel was never exercised. If a stub can't reproduce the real effect, render the real unit and mock only the leaf (network/provider/IPC).
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.
- 1mo ago Changed a65f4f1a935c
- 1mo ago First seen · 59 lines · 48 tokens per session scan A ee18c59b209a
testing-rules is a skill published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed today), licensed Apache-2.0. It adds 48 tokens to every session and 1,561 once invoked, about $0.0002 per session on Opus 5.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
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history, or import a local recording. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
tauri-pilot
Inspect, interact with, and test a running Tauri v2 app via CLI. Communicates over Unix socket using JSON-RPC 2.0. Use when testing UI, automating interactions, or debugging a Tauri app.
systematic-debugging
4-phase systematic debugging methodology with root cause analysis and evidence-based verification. Use when debugging complex issues.
tdd-workflow
Test-Driven Development workflow principles. RED-GREEN-REFACTOR cycle, writing failing tests first, and enforcing behavioral verification.
testing-patterns
Testing patterns and principles. Unit, integration, mocking strategies, Arrange-Act-Assert (AAA), and multi-ecosystem test runners.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.