Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftnpx agentmods add commands/thebeardedbearsas/claude-craft/native-moduleWrote 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/native-module)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/native-module"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/native-module/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/native-module"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/native-module.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.00008 | $0.03852 |
| Opus 5.5 | $0.00003 | $0.01541 |
| Sonnet 5.5 | $0.00002 | $0.00770 |
| Haiku 4.5 | $0.00001 | $0.00385 |
Grade A, and why
native-module 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 1mo 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 — 608 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide Création Module Natif React Native
Tu es un développeur React Native senior. Tu dois guider la création d'un module natif (bridge) pour iOS et Android.
Arguments
$ARGUMENTS
Arguments :
- Nom du module (ex:
DeviceInfo,Biometrics,FileManager) - (Optionnel) Fonctionnalités : sync, async, events
Exemple : /reactnative:native-module Biometrics async,events
MISSION
Étape 1 : Structure du Module
src/
└── native/
└── {ModuleName}/
├── index.ts # API JavaScript
├── types.ts # Types TypeScript
└── NativeModule.ts # Bridge avec TurboModule
android/
└── app/src/main/java/com/{package}/
└── {modulename}/
├── {ModuleName}Module.kt # Module principal
└── {ModuleName}Package.kt # Package registration
ios/
└── {AppName}/
├── {ModuleName}.swift # Module Swift
└── {ModuleName}-Bridging-Header.h # Header pour Obj-C bridge
Étape 2 : API JavaScript/TypeScript
// src/native/{ModuleName}/types.ts
export interface {ModuleName}Result {
success: boolean;
data?: unknown;
error?: string;
}
export interface {ModuleName}Options {
timeout?: number;
// ...autres options
}
export type {ModuleName}EventType = 'onProgress' | 'onComplete' | 'onError';
export interface {ModuleName}Event {
type: {ModuleName}EventType;
payload: unknown;
}
// src/specs/Native{ModuleName}.ts ← Codegen spec (New Architecture RN 0.85+)
import type { TurboModule } from 'react-native';
import { TurboModuleRegistry } from 'react-native';
// Codegen génère les bindings C++/ObjC/Java à partir de cette spec TypeScript.
// Exécuter `pod install` (iOS) ou `./gradlew generateCodegenArtifacts` (Android)
// après toute modification de cette interface.
export interface Spec extends TurboModule {
// Méthode synchrone via JSI (réserver aux opérations < 1 ms)
getConstant(): string;
// Méthodes asynchrones
authenticate(options: {[key: string]: unknown}): Promise<{[key: string]: unknown}>;
isSupported(): Promise<boolean>;
// Événements (Fabric EventEmitter)
addListener(eventType: string): void;
removeListeners(count: number): void;
}
// TurboModuleRegistry.getEnforcing lève une erreur claire si le module
// n'est pas lié — remplace l'ancien pattern NativeModules.{ModuleName} + Proxy.
export default TurboModuleRegistry.getEnforcing<Spec>('{ModuleName}');
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.
- 1mo ago First seen · 608 lines · 8 tokens per session scan A 658e4a01dc11
native-module is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 3,852 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
perf-investigate
Drive an iOS performance or memory-leak investigation on using Memory Graph + Time Profiler. Enforce data-before-architecture and stacked PRs.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.