Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dpearson2699/device-integrity
Verify device legitimacy and app integrity using DeviceCheck (DCDevice per-device bits) and App Attest (DCAppAttestService key generation, attestation, and assertion flows).
Passed 22 of 22 test cases with the skill, and 17 of 22 without it.
and 5 more in the full report
5 fixed17 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
When sending an attested API request from an iOS client to a backend server, what custom HTTP headers are conventionally used to transmit the base64 assertion string and base64 client data payload?
| Checked | Without skill | With skill |
|---|---|---|
| Sets X-App-Attest-Assertion header for assertion string | Missed | Passed |
| Sets X-App-Attest-Client-Data header for client data payload | Missed | Passed |
The instructions your model reads when the skill loads.
Verify that requests to your server come from a genuine Apple device running a legitimate instance of your app. DeviceCheck provides per-device bits for simple flags (e.g., "claimed promo offer"). App Attest uses Secure Enclave keys and Apple attestation to cryptographically prove app legitimacy on sensitive requests.
DCDevice generates a
unique, ephemeral token that identifies a device. Treat each token as
single-use: generate a new token for each server operation instead of caching or
reusing one. The token is sent to your server, which then communicates with
Apple's servers to read or set two per-device bits. Available on iOS 11+.
import DeviceCheck
func generateDeviceToken() async throws -> Data {
guard DCDevice.current.isSupported else {
throw DeviceIntegrityError.deviceCheckUnsupported
}
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.