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.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/commands/thebeardedbearsas/claude-craft/store-prepare)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/store-prepare"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/store-prepare/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/commands/thebeardedbearsas/claude-craft/store-prepare"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/store-prepare.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.00005 | $0.03040 |
| Opus 5 | $0.00003 | $0.01520 |
| Sonnet 5 | $0.00001 | $0.00608 |
| Haiku 4.5 | $0.00001 | $0.00304 |
Grade A, and why
store-prepare 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 4d 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checklist Publication Store React Native
Tu es un expert publication mobile. Tu dois préparer l'application pour la soumission sur l'App Store (iOS) et le Google Play Store (Android).
Arguments
$ARGUMENTS
Arguments :
- (Optionnel) Store : ios, android, both
- (Optionnel) Type : new, update
Exemple : /reactnative:store-prepare both new
MISSION
Étape 1 : Checklist Pré-Soumission
══════════════════════════════════════════════════════════════
📱 CHECKLIST PUBLICATION STORE
══════════════════════════════════════════════════════════════
──────────────────────────────────────────────────────────────
🔧 CONFIGURATION TECHNIQUE
──────────────────────────────────────────────────────────────
### Version et Build
[ ] Version incrémentée (semver)
- iOS: CFBundleShortVersionString
- Android: versionName
[ ] Build number incrémenté
- iOS: CFBundleVersion (entier)
- Android: versionCode (entier)
[ ] Changelog préparé pour cette version
### Build de Release
[ ] Mode release configuré (pas de dev mode)
[ ] Bundle JS optimisé
[ ] ProGuard/R8 activé (Android)
[ ] Bitcode désactivé si nécessaire (iOS)
[ ] Hermes activé (recommandé)
### Sécurité
[ ] Clés API en variables d'environnement
[ ] Pas de secrets dans le code
[ ] Certificate pinning si nécessaire
[ ] Keystore signé correctement (Android)
[ ] Provisioning profile valide (iOS)
Étape 2 : Configuration iOS
<!-- ios/{App}/Info.plist -->
<!-- Version -->
<key>CFBundleShortVersionString</key>
<string>1.2.0</string>
<key>CFBundleVersion</key>
<string>45</string>
<!-- Permissions (avec descriptions utilisateur) -->
<key>NSCameraUsageDescription</key>
<string>Cette app utilise la caméra pour scanner des QR codes.</string>
<key>NSPhotoLibraryUsageDescription</key>
<string>Cette app accède à vos photos pour vous permettre de télécharger des images.</string>
<key>NSLocationWhenInUseUsageDescription</key>
<string>Cette app utilise votre position pour afficher les magasins proches.</string>
<key>NSFaceIDUsageDescription</key>
<string>Cette app utilise Face ID pour sécuriser l'accès à votre compte.</string>
<key>NSMicrophoneUsageDescription</key>
<string>Cette app utilise le microphone pour les messages vocaux.</string>
<!-- App Transport Security -->
<key>NSAppTransportSecurity</key>
<dict>
<key>NSAllowsArbitraryLoads</key>
<false/>
<!-- Exceptions si nécessaire -->
</dict>
<!-- Capabilities requises -->
<key>UIRequiredDeviceCapabilities</key>
<array>
<string>armv7</string>
</array>
<!-- Orientations supportées -->
<key>UISupportedInterfaceOrientations</key>
<array>
<string>UIInterfaceOrientationPortrait</string>
</array>
<key>UISupportedInterfaceOrientations~ipad</key>
<array>
<string>UIInterfaceOrientationPortrait</string>
<string>UIInterfaceOrientationLandscapeLeft</string>
<string>UIInterfaceOrientationLandscapeRight</string>
</array>
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.
- 4d ago First seen · 484 lines · 5 tokens per session scan A c56cbddd3c9e
store-prepare is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 5 tokens to every session and 3,040 once invoked, about $0.0000 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 commands, from other repositories
security-scan
Run security audit on codebase.
help
Explain Ralph Wiggum technique and available commands.
speckit.zuraffa.generate-commands
Regenerate all extension command files from zfa manifest.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.