bc-wallet-mobile: Skill for Claude Code

.agents/skills/bcsc-core-native-testing/SKILL.md

bcsc-core-native-testing is a skill for Claude Code, Codex from bcgov/bc-wallet-mobile. It costs 81 tokens per session (2,232 once invoked), scanned A, original, Apache-2.0.

A guide for writing native unit tests for Swift iOS and Kotlin Android code in the bcsc-core package. It covers tests for services such as authentication, PIN management, secure storage, and device authentication.

In plain words
What is it for?
Use it to add XCTest tests on iOS or JUnit tests on Android, including tests that mock native protocols and interfaces.
Why use it?
It helps test native code in isolation, without relying on the full mobile app or real external services. It also explains how to use test doubles, which are substitute objects used to control dependencies during tests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is bcgov/bc-wallet-mobile's own configuration. It tells Claude Code and Codex how to work on bc-wallet-mobile itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bc-wallet-mobile configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/bcgov/bc-wallet-mobile/main/.agents/skills/bcsc-core-native-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/bcgov/bc-wallet-mobile

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for bcsc-core-native-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/bcgov/bc-wallet-mobile/bcsc-core-native-testing.svg)](https://agentmods.dev/skills/bcgov/bc-wallet-mobile/bcsc-core-native-testing)
Your own site
<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>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,232 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 196eb3b6a621, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

.agents/skills/bcsc-core-native-testing/SKILL.md · 211 lines

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:

  • BcscCoreTestable target: A subset of production iOS source files compiled for the simulator (without React Native / CocoaPods dependencies). Only files listed in the sources: array are included.
  • BcscCoreTests test target: XCTest files under ios/BcscCoreTests/, compiled with @testable import BcscCoreTestable.
  • SPM_BUILD flag: A Swift compiler define set in Package.swift via swiftSettings: [.define("SPM_BUILD")]. The file ios/SPMCompat.swift uses #if SPM_BUILD to 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
  1. Create a new .swift file in ios/BcscCoreTests/.
  2. Import frameworks and the testable module:
    import LocalAuthentication  // if testing LAPolicy/biometric types
    import XCTest
    @testable import BcscCoreTestable
    
  3. Write XCTestCase subclasses. Follow the naming convention {ClassUnderTest}Tests.
  4. Run with yarn test:ios or directly:
    xcodebuild test -scheme BcscCoreTests-Package \
      -destination 'platform=iOS Simulator,name=iPhone 16,OS=latest' \
      -skipPackagePluginValidation
    

Read the full file on GitHub · 211 lines

Changes

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.

  1. 3d ago First seen · 211 lines · 81 tokens per session scan A 196eb3b6a621

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories