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 sgaabdu4/hard-eng --skill diagnose-flutter-mobile-runtimegit clone --depth 1 https://github.com/sgaabdu4/hard-engWrote 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/sgaabdu4/hard-eng/diagnose-flutter-mobile-runtime)<a href="https://agentmods.dev/skills/sgaabdu4/hard-eng/diagnose-flutter-mobile-runtime"><img src="https://agentmods.dev/badge/skills/sgaabdu4/hard-eng/diagnose-flutter-mobile-runtime/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/sgaabdu4/hard-eng/diagnose-flutter-mobile-runtime"><img src="https://agentmods.dev/badge/skills/sgaabdu4/hard-eng/diagnose-flutter-mobile-runtime.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.00077 | $0.00694 |
| Opus 5 | $0.00039 | $0.00347 |
| Sonnet 5 | $0.00015 | $0.00139 |
| Haiku 4.5 | $0.00008 | $0.00069 |
Grade A, and why
diagnose-flutter-mobile-runtime 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 10d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Diagnose Flutter Mobile Runtime
Contract
- Owner = cross-layer seam isolation; causal synthesis remains
diagnosing-bugs. - Before native, provider, backend, or device action = read runtime-seam-ladder.md.
- Start = reporter ledger + red-capable user-visible reproduction + exact artifact/device/account/environment identity.
- Proceed one seam at a time; first red/unknown prerequisite cancels downstream retries.
- Installed dependency + present manifest entry + successful provider request + green widget test = wiring evidence only.
- Reinstall = fresh app-instance perturbation; invalidate token, installation, permission, session, and prior delivery evidence.
- Every plugin/external observation = bounded deadline + captured terminal result; indefinite wait or blind polling =
FAIL. - Product timeout/fallback change = explicit fix authority + defined user-visible semantics + regression proof; diagnostic timeout alone never selects the fix.
- Source mutation = forbidden without explicit fix authority.
Route
| Need | Owner |
|---|---|
| Reproduction + mechanism + blast radius | diagnosing-bugs |
| Current OS/plugin/provider contract | research |
| Flutter/Riverpod/native packaging change | building-flutter-apps |
| Appwrite provider/target/message/CLI seam | appwrite-backend |
| Sentry issue/release evidence | sentry |
| Real device/UI behavior | e2e |
| Commands + gates + retry readiness | deterministic-checks |
| Proven recurrence | repeated-failure-learning → he-learn |
Workflow
- Build the closure matrix from the reference; include every user-named platform, artifact, lifecycle state, permission state, and delivery path.
- Bind local versions + exact target identity; verify current external contracts through
researchbefore platform-dependent diagnosis or repair. - Reproduce once at the public seam; descend the ladder until the first red/unknown boundary.
- Prove the owner/mechanism with one discriminating check; do not reinstall, resend, rebuild, or vary payloads as a substitute.
- With fix authority, repair the narrowest owner → rerun original red proof → affected downstream states → full requested matrix.
- Close test data, processes, temporary artifacts, and every reporter-ledger item.
What ships with it
2 files 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.
- 10d ago First seen · 51 lines · 77 tokens per session scan A d1282380c914
diagnose-flutter-mobile-runtime is a skill published in the GitHub repository sgaabdu4/hard-eng (5 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 694 once invoked, about $0.0004 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-30.
Other skills, from other repositories
rn-debugging
This skill should be used when the user asks to "debug the app", "fix a crash", "diagnose a blank screen", "read error logs", "troubleshoot CDP connection", "check Metro status", "find native crashes", "inspect network failures", "the app crashed", "I see a blank screen", "the screen is white", "something broke", "app…
performance-profiling
Instruments integration and performance analysis workflows for iOS apps. Use when profiling CPU usage, memory allocation, network activity, or energy consumption. Covers Time Profiler, Allocations, Leaks, Network instruments, and performance optimization strategies.
crash-debugging
Crash log analysis, symbolication, and debugging workflows for iOS apps. Use when investigating app crashes, analyzing crash reports, symbolicating stack traces, or identifying root causes. Covers crash log retrieval, symbolication with dSYM files, stack trace analysis, and common crash patterns.
debugging-and-error-recovery
Use when encountering unexpected behavior, crashes, or test failures in Android. Six-step triage from reproduction to regression guard, using Logcat, Android Studio debugger, and profiling tools.
competition-ios-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift…
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.