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.
/plugin marketplace add firebase/firebase-toolsnpx agentmods add plugins/firebase/firebase-tools/marketplacegit clone --depth 1 https://github.com/firebase/firebase-toolsGrade A, and why
firebase 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 yesterday.
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
{
"name": "firebase",
"owner": {
"name": "Firebase",
"email": "[email protected]"
},
"metadata": {
"description": "Official Claude plugin for Firebase to help understand and manage your Firebase project, resources, and data",
"version": "1.0.0"
},
"plugins": [
{
"name": "firebase",
"description": "Claude plugin for Firebase that installs the Firebase MCP server and helps to manage Firebase projects, add backend services, add AI features, deploy & host apps, and more",
"version": "1.0.0",
"author": {
"name": "Firebase",
"url": "https://firebase.google.com/"
},
"homepage": "https://github.com/firebase/firebase-tools",
"repository": "https://github.com/firebase/firebase-tools.git",
"license": "MIT",
"keywords": [
"firebase",
"mcp",
"cloud",
"firestore",
"database",
"hosting",
"functions",
"cli"
],
"category": "development",
"tags": ["firebase", "backend", "database", "cloud-services"],
"mcpServers": {
"firebase": {
"description": "Firebase MCP server for understanding and managing your Firebase project, resources, and data",
"command": "npx",
"args": ["-y", "firebase-tools", "mcp", "--dir", "."],
"env": {
"IS_FIREBASE_MCP": "true"
}
}
},
"source": "./"
}
]
}
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.
- yesterday First seen · 49 lines scan A ad10a16088e5
firebase is a plugin published in the GitHub repository firebase/firebase-tools (4,463 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
ai-skills
Plugin marketplace listing 8 plugins: security-hooks, pr-review-triage, dev-skills, nix-skills, git-workflow.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.