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/localization-check)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/localization-check"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/localization-check/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/localization-check"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/localization-check.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.00006 | $0.02045 |
| Opus 5.5 | $0.00002 | $0.00818 |
| Sonnet 5.5 | $0.00001 | $0.00409 |
| Haiku 4.5 | $0.00001 | $0.00204 |
Grade A, and why
localization-check 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vérification des Traductions
Tu es un développeur Flutter senior. Tu dois vérifier la complétude et la cohérence des traductions (i18n) du projet.
Arguments
$ARGUMENTS
Arguments :
- (Optionnel) Langue à vérifier (ex:
fr,en,all)
Exemple : /flutter:localization-check all
MISSION
Étape 1 : Identifier la Configuration i18n
# pubspec.yaml
dependencies:
flutter_localizations:
sdk: flutter
intl: ^0.19.0
flutter:
generate: true
# l10n.yaml
arb-dir: lib/l10n
template-arb-file: app_en.arb
output-localization-file: app_localizations.dart
output-class: AppLocalizations
Étape 2 : Analyser les Fichiers ARB
# Lister les fichiers de traduction
ls -la lib/l10n/
# Générer les fichiers Dart
flutter gen-l10n
Étape 3 : Vérifier les Clés
// Script de vérification (à exécuter manuellement ou via test)
import 'dart:convert';
import 'dart:io';
void main() {
final arbFiles = Directory('lib/l10n')
.listSync()
.whereType<File>()
.where((f) => f.path.endsWith('.arb'));
final Map<String, Map<String, dynamic>> translations = {};
for (final file in arbFiles) {
final lang = file.path.split('app_').last.replaceAll('.arb', '');
final content = jsonDecode(file.readAsStringSync()) as Map<String, dynamic>;
translations[lang] = content;
}
// Trouver la langue de référence (template)
final reference = translations['en']!;
final referenceKeys = reference.keys
.where((k) => !k.startsWith('@'))
.toSet();
print('Reference language: en');
print('Keys count: ${referenceKeys.length}');
print('');
for (final entry in translations.entries) {
if (entry.key == 'en') continue;
final keys = entry.value.keys
.where((k) => !k.startsWith('@'))
.toSet();
final missing = referenceKeys.difference(keys);
final extra = keys.difference(referenceKeys);
print('Language: ${entry.key}');
print(' Keys: ${keys.length}');
print(' Missing: ${missing.length}');
print(' Extra: ${extra.length}');
if (missing.isNotEmpty) {
print(' Missing keys:');
for (final key in missing) {
print(' - $key');
}
}
print('');
}
}
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 · 317 lines · 6 tokens per session scan A 0c8b4c26b6c3
localization-check is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 7d ago), licensed MIT. It adds 6 tokens to every session and 2,045 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
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
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.