Borrowing it
Nothing to install: this file belongs to bcgov/bc-wallet-mobile. 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/bcgov/bc-wallet-mobile/main/.agents/skills/bcsc-core-native-testing/SKILL.mdgit clone --depth 1 https://github.com/bcgov/bc-wallet-mobileWrote 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/bcgov/bc-wallet-mobile/bcsc-core-native-testing)<a href="https://agentmods.dev/skills/bcgov/bc-wallet-mobile/bcsc-core-native-testing"><img src="https://agentmods.dev/badge/skills/bcgov/bc-wallet-mobile/bcsc-core-native-testing.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.00081 | $0.02232 |
| Opus 5 | $0.00041 | $0.01116 |
| Sonnet 5 | $0.00016 | $0.00446 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
bcsc-core-native-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 3d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bcsc-core Native Unit Testing
Overview
This skill guides creation of native unit tests for the packages/bcsc-core module, which contains Swift (iOS) and Kotlin (Android) implementations of authentication, PIN management, keychain storage, token services, and device authentication.
The codebase already uses protocol-based dependency injection on iOS and interface/class-based injection on Android, making it straightforward to create mock implementations for isolated unit testing.
Test Infrastructure
iOS — XCTest via SPM
Tests are built with Swift Package Manager using the package manifest at packages/bcsc-core/Package.swift. The key concepts:
BcscCoreTestabletarget: A subset of production iOS source files compiled for the simulator (without React Native / CocoaPods dependencies). Only files listed in thesources:array are included.BcscCoreTeststest target: XCTest files underios/BcscCoreTests/, compiled with@testable import BcscCoreTestable.SPM_BUILDflag: A Swift compiler define set inPackage.swiftviaswiftSettings: [.define("SPM_BUILD")]. The fileios/SPMCompat.swiftuses#if SPM_BUILDto provide lightweight stubs (e.g.,SecureRandom,Data.arrayOfBytes()) for types from JWE files that aren't included in the SPM target.- Scheme name: xcodebuild uses
BcscCoreTests-Package(SPM auto-appends-Package).
Adding a new iOS source file to the test target
If the code under test references types in a file not yet in Package.swift, add it to the sources: array in the BcscCoreTestable target. If that file depends on types from excluded files (e.g., JWE/crypto), add stubs to SPMCompat.swift behind #if SPM_BUILD.
Adding a new iOS test file
- Create a new
.swiftfile inios/BcscCoreTests/. - Import frameworks and the testable module:
import LocalAuthentication // if testing LAPolicy/biometric types import XCTest @testable import BcscCoreTestable - Write
XCTestCasesubclasses. Follow the naming convention{ClassUnderTest}Tests. - Run with
yarn test:iosor directly:xcodebuild test -scheme BcscCoreTests-Package \ -destination 'platform=iOS Simulator,name=iPhone 16,OS=latest' \ -skipPackagePluginValidation
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.
- 3d ago First seen · 211 lines · 81 tokens per session scan A 196eb3b6a621
bcsc-core-native-testing is a skill published in the GitHub repository bcgov/bc-wallet-mobile (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 81 tokens to every session and 2,232 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-09-03.
Other skills, from other repositories
swift-protocol-di-testing
Protocol-based dependency injection for testable Swift code — mock file system, network, and external APIs using focused protocols and Swift Testing.
android-unit-test
Guide for writing and converting Chromium Android unit tests across host Robolectric (chromejunittests) and on-device (chromepublicunittestapk) suites.
react-native-testing
Write tests using React Native Testing Library (RNTL) v13 and v14 (@testing-library/react-native). Use when writing, reviewing, or fixing React Native component tests. Covers: render, screen, queries (getBy/getAllBy/queryBy/findBy), Jest matchers, userEvent, fireEvent, waitFor, and async patterns. Supports v13 (React…
flutter-add-widget-test
Implement a component-level test using WidgetTester to verify UI rendering and user interactions (tapping, scrolling, entering text). Use when validating that a specific widget displays correct data and responds to events as expected.
mobiai-android-testing
Use when writing or running tests in an Android project — unit tests, UI tests, choosing the right framework and patterns.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.