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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill testflight-release-notesgit 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/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/testflight-release-notes)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/testflight-release-notes"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/testflight-release-notes/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/testflight-release-notes"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/testflight-release-notes.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.00110 | $0.01030 |
| Opus 5.5 | $0.00044 | $0.00412 |
| Sonnet 5.5 | $0.00022 | $0.00206 |
| Haiku 4.5 | $0.00011 | $0.00103 |
Grade A, and why
testflight-release-notes 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 12d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestFlight Release Notes
Produces the text testers see when they tap "What to Test" in TestFlight, and (with the length and tone tweaks below) the App Store "What's New" text. Input is whatever the developer has: git log, bullets, issue titles, or almost nothing.
Method
- Collect changes. If the user gave none, gather commits since the last tag (or a ref they name):
git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD --oneline - Filter to user-impacting changes only (see below).
- Translate each into what the person using the app experiences.
- Group into sections, apply tone and length rules, output plain text.
Filtering
Skip internal noise testers never see or feel:
- Dependency updates and lockfile changes
- Version and build number bumps
- Merge commits
- CI/CD changes
- Refactors with no visible effect
- Work behind feature flags (unless the flag is being enabled)
- Documentation and test-only changes
Keep anything that changes how the app looks, feels, or behaves.
Output format
Plain text only. TestFlight renders text literally, so no markdown (**, ##, *, links).
- Section headers in ALL CAPS
- List items start with "- "
- Blank line between sections
- Only include sections that have content
Length: TestFlight's limit is 4,000 characters for What to Test. If over, keep the most impactful changes. For App Store "What's New", aim for a short paragraph or a handful of bullets (hard limit 4,000 characters, but shorter is better) and drop the WHAT TO TEST and KNOWN ISSUES sections, which belong to beta builds only.
Section order
- Build line: "Build [number]" only if the developer provided one. Never guess a number.
- WHAT'S NEW: brand-new features or capabilities.
- IMPROVEMENTS: existing things that work or look better.
- BUG FIXES: describe the symptom, not the cause ("Fixed a crash when opening the settings screen", not "Fixed nil unwrap in SettingsViewModel").
- KNOWN ISSUES: only if the developer mentioned them. Do not invent.
- WHAT TO TEST: only if the developer asked testers to focus somewhere. Be specific ("Create a new item and check the total updates immediately", not "Test items").
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 96 lines · 110 tokens per session scan A 58de24b8da73
testflight-release-notes is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 110 tokens to every session and 1,030 once invoked, about $0.0004 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-10-15.
Other skills, from other repositories
offensive-mobile
Mobile (Android + iOS) application penetration testing methodology. Covers static analysis (apktool/jadx for Android, class-dump/Hopper/IDA for iOS), dynamic instrumentation with Frida and Objection, SSL pinning bypass strategies, root/jailbreak detection bypass, deep-link / URL-scheme abuse, exported component…
android-dev
Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.
flutter
Use when building Flutter applications. Covers widget composition, state management, build-method performance, platform channels, and the rendering behavior behind most Flutter jank. Trigger on "my flutter app is janky", "too many rebuilds", "riverpod or bloc", "call native code from flutter". Do not use for store…
ios
Use when building native iOS applications. Covers SwiftUI architecture, state management, navigation, networking, persistence, background behavior, and App Store submission requirements. Trigger on "structure my swiftui app", "deep links open the wrong screen", "background fetch isn't running". Do not use for Swift…
mobile-release
Use when preparing a mobile app for release. Covers versioning, signing, staged rollout, crash monitoring, store review requirements, and rollback when an update goes wrong. Trigger on "ready to submit to the app store", "app got rejected in review", "crash rate spiked after the update", "set up a staged rollout". Do…
react-native
Use when building cross-platform mobile apps with React Native or Expo. Covers navigation, platform differences, list performance, native modules, offline behavior, and release builds. Trigger on "flatlist is laggy", "expo or bare react native", "bridge to a native module", "set up ota updates". Do not use for web…