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 agentmods add skills/sonature-lab/timsquad/monitoringnpx skills add sonature-lab/timsquad --skill monitoringgit clone --depth 1 https://github.com/sonature-lab/timsquadWrote 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/sonature-lab/timsquad/monitoring)<a href="https://agentmods.dev/skills/sonature-lab/timsquad/monitoring"><img src="https://agentmods.dev/badge/skills/sonature-lab/timsquad/monitoring.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 | $0.00036 | $0.01021 |
| Opus 5 | $0.00018 | $0.00511 |
| Sonnet 5 | $0.00007 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
monitoring 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitoring & Analytics
Flutter 앱 모니터링 통합 가이드. Firebase Crashlytics + Analytics + Performance, Sentry, 구조화된 로깅으로 프로덕션 품질을 수치로 관리.
Philosophy
- 크래시는 0순위 — Crashlytics 비활성화 금지, 모든 비치명 에러도 기록
- 이벤트는 설계 — 무분별한 로깅 금지, 이벤트 택소노미 먼저 정의
- 성능은 측정 — 체감이 아닌 custom trace와 HTTP metric으로 수치화
Resources
5개 규칙 + 1개 참조. 크래시부터 로깅까지 모니터링 파이프라인 전체를 커버.
| Priority | Type | Resource | Description |
|---|---|---|---|
| CRITICAL | rule | crashlytics-setup | Crashlytics 초기화, 에러 캡처, 사용자 식별 |
| HIGH | rule | analytics | Analytics 이벤트 택소노미, 사용자 속성, 화면 추적 |
| HIGH | rule | performance-monitoring | Performance custom trace, HTTP metric, 프레임 모니터링 |
| MEDIUM | rule | sentry-integration | Sentry 초기화, breadcrumbs, scope, Crashlytics 공존 |
| MEDIUM | rule | logging | 구조화된 로깅, 레벨 관리, 민감 데이터 마스킹 |
| — | ref | monitoring-architecture | 모니터링 레이어, 대시보드, 알림, 데이터 보존 |
Quick Rules
Crashlytics
FlutterError.onError = FirebaseCrashlytics.instance.recordFlutterFatalErrorPlatformDispatcher.instance.onError→ 비동기 에러 캡처- 비치명 에러 →
recordError(error, stack, fatal: false) setUserIdentifier→ 크래시와 사용자 매핑setCustomKey→ 디바이스 상태, 기능 플래그 등 컨텍스트
Analytics
- 이벤트 택소노미 먼저 정의 (screen_view, button_click, feature_use)
setUserProperty→ user_type, subscription_tier 등 세그먼트 기준AnalyticsObserver→ go_router 화면 전환 자동 추적- 디버그 →
adb shell setprop debug.firebase.analytics.app <package>
Performance
FirebasePerformance.instance.newTrace('name')→ custom trace- HTTP metric → 자동 수집 (dio interceptor 또는 http_client)
- 느린 프레임 임계값 16ms (60fps), 8ms (120fps)
Sentry
SentryFlutter.init→ DSN 환경별 분리 (dev/staging/prod)Sentry.addBreadcrumb→ 네비게이션, HTTP, 사용자 액션 추적- Crashlytics + Sentry 공존 → 각자 역할 분리 (crash vs context)
Logging
logger패키지 → 레벨별 색상 출력 (개발), JSON 구조화 (프로덕션)- 릴리스 빌드 → verbose/debug 레벨 비활성화
- 민감 데이터 (토큰, PII) → 마스킹 필수
What ships with it
6 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.
- 5d ago First seen · 82 lines · 36 tokens per session scan A f3d34950abc4
monitoring is a skill published in the GitHub repository sonature-lab/timsquad (11 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 1,021 once invoked, about $0.0002 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
update-store
ストア情報の更新自動化 — スクリーンショット撮影（シミュレーター × モック画面 × Marionette MCP）とメタデータテキスト更新。ストア更新、スクショ更新、App Store / Google Play のメタデータ更新、リリースノート作成の際に使用すること。.
mobile-automation
MCP (dart-mcp + Marionette) を使ったFlutterアプリのE2E自動化・UI検証ガイド。シミュレーターでのUI動作確認、モックプレビュー検証、Bridge経由のE2Eテスト、スクリーンショット撮影など、アプリの動作検証が必要なときに使う。「動作確認して」「UIを検証して」「E2Eテスト」「シミュレーターで確認」「モックで確認」と言われたときや、UI変更後の検証フェーズで使用すること。.
submit-store-review
App Store Connect・Google Playの現在の公開版をAPIで調べ、既存の最新安定ビルドとの差分から4言語のリリースノートを作成し、CLI/APIで審査へ提出・再提出する。新しいビルドを作るrelease-appとは分離し、「最新を審査提出して」「ストア審査へ提出して」「App Reviewに出して」「Google Playの審査を進めて」「却下対応して再提出して」と依頼されたときに使用する。.
flutter-ui-design
SSOT (Single Source of Truth) + UDF (Unidirectional Data Flow) に基づく設計。.
release-app
アプリのリリース（バージョンbump + CHANGELOG + タグ → GH Actions で自動ビルド・配布）。iOS / Android / macOS / Linux / Windows の任意の組み合わせでリリースできる。「リリース」「バージョン上げて」「リリースして」と言われたときに使う。.
flutter-upgrade
Flutter SDKバージョンアップグレード対応。新バージョンのリリースノート・Breaking Changes調査、コードベース影響分析、mise/CI/Shorebird含むプロジェクト全体の対応タスクリスト作成と実行。「Flutterアップグレード」「Flutter X.Y.Zがリリースされた」「Flutter最新化」「Flutter更新」と言われたとき、またはFlutterの新バージョンについて言及されたときに使用する。.