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 wangjianqi/AppStore --skill 13-testinggit clone --depth 1 https://github.com/wangjianqi/AppStoreWrote 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/wangjianqi/appstore/13-testing)<a href="https://agentmods.dev/skills/wangjianqi/appstore/13-testing"><img src="https://agentmods.dev/badge/skills/wangjianqi/appstore/13-testing/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/wangjianqi/appstore/13-testing"><img src="https://agentmods.dev/badge/skills/wangjianqi/appstore/13-testing.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.00034 | $0.02583 |
| Opus 5.5 | $0.00014 | $0.01033 |
| Sonnet 5.5 | $0.00007 | $0.00517 |
| Haiku 4.5 | $0.00003 | $0.00258 |
Grade A, and why
testing 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
测试
测试分层
| 层级 | 类型 | 占比 | 速度 | 目标 |
|---|---|---|---|---|
| ViewModel / Service | 单元测试 | 70% | 快(< 0.1s) | 逻辑正确性 |
| Repository / Storage | 集成测试 | 20% | 中(< 1s) | 数据层协作 |
| ViewController | UI 测试 | 10% | 慢(> 2s) | 关键用户流程 |
原则:
- ViewModel 和 Service 是测试重点,覆盖率目标 > 80%
- VC 不写单元测试(太脆弱),用 UI 测试覆盖关键路径
- Repository 层用内存数据库测试,不依赖真实 CoreData
项目配置
目录约定
AppTests/
├── ViewModels/ # ViewModel 单元测试
│ └── CameraViewModelTests.swift
├── Services/ # Service 单元测试
│ └── AuthServiceTests.swift
├── Repositories/ # Repository 集成测试
│ └── UserRepositoryTests.swift
├── UI/ # UI 测试
│ └── LoginFlowTests.swift
├── Helpers/ # 测试辅助
│ ├── MockNetworkService.swift
│ ├── StubData.swift
│ └── CoreDataTestStack.swift
└── Extensions/ # 测试扩展
└── XCTestCase+Async.swift
测试 Target 配置
- Unit Test Target:
AppTests,Host Application 设为主 App - UI Test Target:
AppUITests,独立进程运行 @testable import App允许访问 internal 成员
单元测试
ViewModel 测试模板
import XCTest
@testable import App
final class CameraViewModelTests: XCTestCase {
private var sut: CameraViewModel!
private var mockCameraService: MockCameraService!
override func setUp() {
super.setUp()
mockCameraService = MockCameraService()
sut = CameraViewModel(cameraService: mockCameraService)
}
override func tearDown() {
sut = nil
mockCameraService = nil
super.tearDown()
}
func testStartCapture_whenAuthorized_callsServiceStart() async {
mockCameraService.authorizationStatus = .authorized
await sut.startCapture()
XCTAssertTrue(mockCameraService.startCaptureCalled)
}
func testStartCapture_whenDenied_showsAlert() async {
mockCameraService.authorizationStatus = .denied
await sut.startCapture()
XCTAssertTrue(sut.showPermissionAlert)
XCTAssertFalse(mockCameraService.startCaptureCalled)
}
}
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 First seen · 372 lines · 34 tokens per session scan A cf506d48db57
testing is a skill published in the GitHub repository wangjianqi/AppStore (17 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 2,583 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
test-writer
Write tests with TDD following structured patterns. Ensures consistent AAA structure, proper coverage targets, and framework-specific conventions. Without this skill, tests lack consistent naming, miss coverage targets, and skip anti-pattern checks.
dotnet-testing-advanced-tunit-advanced
A guide for advanced TUnit testing in .NET. TUnit is a testing framework; the guide covers tests driven by data, dependency injection, integration tests, retries, time limits, and filtering.
testing-patterns
Testing patterns for unit, integration, and end-to-end tests. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.
ios-testing
Invoke any time a user is writing iOS/Swift tests or asking why tests behave a certain way — including XCTest versus Swift Testing (@Test/#expect) choices, async ViewModel tests with @Observable or @Published, snapshot testing across device sizes, mocking protocols for dependency injection, setUp/tearDown lifecycle…
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…