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/obiwancenobi/klambenWrote 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/obiwancenobi/klamben/check-platform)<a href="https://agentmods.dev/commands/obiwancenobi/klamben/check-platform"><img src="https://agentmods.dev/badge/commands/obiwancenobi/klamben/check-platform.svg" alt="Measured on agentmods" 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.00029 | $0.00451 |
| Opus 5 | $0.00015 | $0.00226 |
| Sonnet 5 | $0.00006 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
check-platform 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 7d 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.
What it actually says
/check-platform
Audit platform adaptation. Mobile apps must feel native on both iOS and Android — this command finds the gaps.
When to use
- Before a cross-platform release
- After adding a new screen
- User asks "does this work on iOS" / "is this Cupertino-ready"
Checks
- Check design context: If
.klamben.mdexists in the project root, read it first. Apply the project's brand, platform targets, accessibility tier, and existing patterns to your work below. - Platform-specific code paths —
Platform.isIOSbranches using Material widgets (and vice versa) - Missing .adaptive constructors —
SwitchnotSwitch.adaptive,Slidernot.adaptive - Navigation patterns —
MaterialPageRouteon iOS withoutCupertinoPageRoutefallback - Dialog style —
AlertDialognotshowAdaptiveDialog - Scroll physics — missing
BouncingScrollPhysicson iOS paths - Typography — Roboto on iOS (San Francisco expected)
- Status bar — dark icons on light bg without
SystemUiOverlayStyleapplied
Output format
Platform check for lib/screens/profile.dart
ISSUES
14:8 Switch used — consider Switch.adaptive
→ Use Switch.adaptive(value: ..., onChanged: ...)
28:3 AlertDialog used — consider showAdaptiveDialog
→ showAdaptiveDialog(context: ..., builder: ...)
42:11 BottomNavigationBar on iOS path without CupertinoTabBar
→ Use PlatformTabScaffold or branch on Platform.isIOS
OK
- No Material widgets under Platform.isIOS branches
- Navigator pushes use adaptive route
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.
- 7d ago First seen · 56 lines · 29 tokens per session scan A c29c9e79c9eb
check-platform is a command published in the GitHub repository obiwancenobi/klamben (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 451 once invoked, about $0.0001 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-08-31.
Other commands, from other repositories
speckit.zuraffa.generate-commands
Regenerate all extension command files from zfa manifest.
building-flutter-apps-skill-ac1294fc
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
audit
Audit the current codebase for Flutter best practice violations.
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.