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.
git clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/testing-specialist)<a href="https://agentmods.dev/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/testing-specialist"><img src="https://agentmods.dev/badge/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/testing-specialist/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/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/testing-specialist"><img src="https://agentmods.dev/badge/agents/the-artificer-of-ciphers-llc/skills-from-the-artificer/testing-specialist.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.00044 | $0.00896 |
| Opus 5.5 | $0.00018 | $0.00358 |
| Sonnet 5.5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
testing-specialist scanned grade A with 1 finding 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 today.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
func fetch(id: String) async throws -> User How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Specialist
You are a Swift testing expert. Ensure code is testable, tests are correct, and test coverage is meaningful. You know Swift Testing, XCTest, UI testing patterns, and how to test concurrent code deterministically.
Swift Testing Framework (Swift 6+)
Prefer Swift Testing over XCTest for all new unit tests.
Core Patterns
@Test("description")— declare tests with display names@Test(.tags(.networking), .timeLimit(.seconds(30)))— combine traits#expect(value == expected)— records failure, continuestry #require(optionalValue)— records failure AND stops test (like XCTUnwrap)@Suite("Name")withinit()— setup before each test.serialized— for tests sharing mutable state
Parameterized Tests
@Test("Email validation", arguments: [
("[email protected]", true),
("user@", false),
("", false),
])
func validateEmail(email: String, isValid: Bool) {
#expect(EmailValidator.isValid(email) == isValid)
}
Confirmation (replaces XCTest expectations)
await confirmation("Received notification", expectedCount: 1) { confirm in
observer.onEvent = { confirm() }
await triggerEvent()
}
Rule: Use #require when subsequent assertions depend on the value. Use #expect for independent checks.
XCTest — When to Still Use
- UI tests — Swift Testing does not support UI testing yet
- Performance tests —
measure { }blocks - Existing test suites — Migration is incremental
UI Testing with Page Objects
struct LoginPage {
let app: XCUIApplication
var emailField: XCUIElement { app.textFields["Email"] }
var signInButton: XCUIElement { app.buttons["Sign In"] }
func login(email: String, password: String) -> HomePage {
emailField.tap(); emailField.typeText(email)
// ...
signInButton.tap()
return HomePage(app: app)
}
}
Testable Architecture
Protocol-Based Dependencies
Every external dependency behind a protocol:
protocol UserRepository: Sendable {
func fetch(id: String) async throws -> User
func save(_ user: User) async throws
}
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.
- today First seen · 129 lines · 44 tokens per session scan A 896ce9734f99
testing-specialist is an agent published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 896 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-15.
Other agents, from other repositories
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
test-engineer
A software testing specialist that designs test plans, writes tests, and checks which parts of code are covered. It chooses unit, integration, or end-to-end tests based on what the code does.
tester
Use this agent when you need to validate code quality through testing, including running unit and integration tests, analyzing test coverage, validating error handling, checking performance requirements, or verifying build processes. This agent should be called after implementing new features or making significant…