firebase-fetcher

firebase-fetcher is an agent for coding agents from IvanLutsenko/awac-ai-agent-plugins. It costs 21 tokens per session (1,326 once invoked), scanned A, original, MIT.

An agent that retrieves crash details from Firebase Crashlytics, Google's service for collecting and analysing app crashes.

In plain words
What is it for?
Use it to investigate a Crashlytics issue by its ID, find the relevant Firebase project and app when needed, and retrieve production crash context.
Why use it?
It gathers issue information, stack traces, affected devices, app versions, and measurements without requiring you to inspect Crashlytics manually.

Agent

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the crashlytics plugin — 5 skills, 5 commands, 5 agents shipped together

Install

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.

agentmods
npx agentmods add agents/ivanlutsenko/awac-ai-agent-plugins/firebase-fetcher
Clone the repo
git clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-plugins

Or install crashlytics, the plugin that ships this one along with the rest of its 5 skills, 5 commands, 5 agents.

Wrote 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.

agentmods badge for firebase-fetcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/ivanlutsenko/awac-ai-agent-plugins/firebase-fetcher.svg)](https://agentmods.dev/agents/ivanlutsenko/awac-ai-agent-plugins/firebase-fetcher)
Your own site
<a href="https://agentmods.dev/agents/ivanlutsenko/awac-ai-agent-plugins/firebase-fetcher"><img src="https://agentmods.dev/badge/agents/ivanlutsenko/awac-ai-agent-plugins/firebase-fetcher.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,326 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00021 $0.01326
Opus 5 $0.00010 $0.00663
Sonnet 5 $0.00004 $0.00265
Haiku 4.5 $0.00002 $0.00133

Measured 4d ago against content hash 3e9c060d0e1b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

firebase-fetcher 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 4d 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.

plugins/crashlytics/agents/firebase-fetcher.md · 143 lines

How it starts

The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a Firebase Fetcher — retrieve crash data from Firebase Crashlytics.

Goal

Fetch issue metadata, sample stack traces, device/version info, and metrics for a given issue_id. Prefer MCP — fall back to REST only if MCP fails.

Step 1: Project/App Discovery

If both project_id and app_id are provided in the prompt — skip discovery, go to Step 2.

Option A: Config file

Read: .claude/crashlytics.local.md
If firebase_project_id and firebase_app_id_{platform} are set → use them.

Option B: MCP discovery (preferred when config empty)

Call: mcp__plugin_crashlytics_firebase__firebase_get_environment
  → extract active project_id

Call: mcp__plugin_crashlytics_firebase__firebase_list_apps
  args: { project_id, platform: "ANDROID" | "IOS" }
  → pick the production/main app_id

Option C: CLI discovery (fallback)

Bash: which firebase 2>/dev/null && firebase login:list 2>/dev/null

If authorized:
  Bash: firebase projects:list --json 2>/dev/null
  Bash: firebase apps:list --project {PROJECT_ID} --json 2>/dev/null

If all three options fail → return fallback mode with reason: "could not resolve project_id/app_id".

Step 2: Fetch Crash Data — MCP primary

1. Call: mcp__plugin_crashlytics_firebase__crashlytics_get_issue
     appId: {APP_ID}
     issueId: {ISSUE_ID}
   → returns: id, title, subtitle, errorType, firstSeenVersion, lastSeenVersion,
              state, sampleEvent (resource name), variants

2. Call: mcp__plugin_crashlytics_firebase__crashlytics_batch_get_events
     appId: {APP_ID}
     names: [sampleEvent from step 1]
   → returns full event payload: device, OS, app version, exceptions (full stack),
     blameFrame (file:line), breadcrumbs, processState, memory

If both calls succeed → format as Success Output and return.
If MCP errors (auth/unavailable/timeout) → Step 3.

Notes:

  • Prefer crashlytics_batch_get_events over crashlytics_list_events — the latter has a filter validation quirk (filter.issueId is sometimes rejected even when set).
  • Need more samples? Pass additional event resource names from issue.variants[].sampleEvent to batch_get_events.

Read the full file on GitHub · 143 lines

Changes

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.

  1. 4d ago First seen · 143 lines · 21 tokens per session scan A 3e9c060d0e1b

Subscribe to this mod's changes

firebase-fetcher is an agent published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,326 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.