Official agent skill

Bug Filing

by SAP in SAP/project-foxhound

File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description.

OfficialGPL-3.0Auto-check passedSecurity

Install Bug Filing

skills CLI
$ npx skills add SAP/project-foxhound --skill bug-filing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install SAP/project-foxhound bug-filing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/SAP/project-foxhound.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bug-filing .claude/skills/bug-filing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bug-filing
GitHub stars
180
Used in
2 other repos
Token cost
~828 tokens
SKILL.md length
373 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
GPL-3.0

At a glance

File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description.

  • Works in 5 steps: Determine the product and component. Run → Choose the bug type (per Mozilla's… → Draft the summary and description and… → …
  • The user asks to file a bug
  • SKILL.md covers Overview, Workflow and Notes
  • Runs Python scripts from its folder; calls python3; reaches tests.firefox.dev

What it does

Bug Filing is an agent skill from SAP/project-foxhound, published by the product's own GitHub organization. File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description. Use when the user asks to file a bug, wants a bug summary/description for a change, or needs to report a defect/enhancement/task. Determines the product and component with mach file-info, drafts the summary and description, and opens a prefilled enterbug.cgi form in the browser for the user to submit.

Its SKILL.md is about 830 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `file-bug.py`).

It sits in Security. The repository describes itself as: A web browser with dynamic data-flow tracking enabled in the Javascript engine and DOM, based on Mozilla Firefox (https://github.com/mozilla-firefox/firefox). It can be used to… The licence is GPL-3.0.

When your agent uses it

  • The user asks to file a bug
  • Wants a bug summary/description for a change
  • Needs to report a defect/enhancement/task

Example prompts

  • “/bug-filing”

Requirements

  • Python 3
  • Pre-approved tools (allowed-tools): Bash(./mach file-info:*), Bash(python3 .agents/skills/bug-filing/file-bug.py:*), Bash(python3 .claude/skills/bug-filing/file-bug.py:*)

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Determine the product and component. Run
  2. Choose the bug type (per Mozilla's task/defect/enhancement guide)
  3. Draft the summary and description and show them to the user.
  4. Confirm with the user before filing. Ask for approval using the
  5. Open the prefilled form. Run the helper script with each Bugzilla

What it can do on your machine

Read from SKILL.md and the folder at commit 9dcb850. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(./mach file-info:*)
    • Bash(python3 .agents/skills/bug-filing/file-bug.py:*)
    • Bash(python3 .claude/skills/bug-filing/file-bug.py:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • tests.firefox.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bug Filing loads about 828 tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 373 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
When it runs · the whole SKILL.md, loaded when a task matches
~828

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SAP/project-foxhound at commit 9dcb850, republished under its GPL-3.0 licence (© SAP). 373 words, ~828 tokens.

Download SKILL.mdSave it as .claude/skills/bug-filing/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
bug-filing
description
File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description. Use when the user asks to file a bug, wants a bug summary/description for a change, or needs to report a defect/enhancement/task. Determines the product and component with `mach file-info`, drafts the summary and description, and opens a prefilled enter_bug.cgi form in the browser for the user to submit.
allowed-tools
Bash(./mach file-info:*), Bash(python3 .agents/skills/bug-filing/file-bug.py:*), Bash(python3 .claude/skills/bug-filing/file-bug.py:*)

Overview

File a Mozilla bug by opening a prefilled Bugzilla "enter bug" form in the user's browser. The skill picks the right component automatically, drafts a well-formatted summary and description, and hands the form to the user to submit, so the bug is created under their own account with a chance to review and adjust.

Workflow

  1. Determine the product and component. Run ./mach file-info bugzilla-component <file> on a representative file the change touches. The output is Product :: Component; split on :: for the product and component URL params.

    • If it returns UNKNOWN, pick the closest sensible component rather than leaving it blank.
  2. Choose the bug type (per Mozilla's task/defect/enhancement guide):

    • defect — shipping software is not behaving as expected: a regression, a crash, an error.
    • enhancement — a new feature or function, or changing how an existing feature behaves.
    • task — change a configuration, update a parameter, or refactor existing code; engineering changes with no user-facing behavior change (tooling, tests, docs, build).
  3. Draft the summary and description and show them to the user.

    • Keep the summary short and specific.
    • In the description, wrap code identifiers (function, variable, class, file, pref, and flag names) in backticks so they render as code in the filed bug.
    • For a test-failure bug, include a link to the test's dashboard: https://tests.firefox.dev/test.html?test=<path>.
  4. Confirm with the user before filing. Ask for approval using the AskUserQuestion tool, with "Looks good, file the bug" as the first (recommended) option so the user can accept it with a single keypress; the automatic "Other" choice lets them request edits instead. Do not run the script until they approve.

  5. Open the prefilled form. Run the helper script with each Bugzilla enter_bug.cgi field as a field=value argument; it URL-encodes the values and opens the form in the browser (cross-platform, so Linux, macOS, and Windows all work):

    python3 .agents/skills/bug-filing/file-bug.py product=<P> component=<C> \
        bug_type=<T> short_desc=<summary> comment=<description>
    • Write short_desc and comment as plain text, with markdown backticks around code identifiers; the script does all the encoding.
    • Any form field works, so add more as the bug needs them, e.g. blocked=<bug> (blocks), dependson=<bug> (depends on), or see_also=<url>.

    The user reviews and submits the form to create the bug, then provides the bug number.

Show full SKILL.md (14 more words)Show less

Notes

  • This skill only opens a prefilled form; it never submits the bug itself.

© SAP, GPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/bug-filing of SAP/project-foxhound.

  • SKILL.md
  • file-bug.py

Open the folder on GitHubat commit 9dcb850

Used in 3 other repositories

We found 7 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in SAP/project-foxhound, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Bug Filing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bug Filing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bug Filing this skillSAP/project-foxhound1802 repos~828Automated safety check: PassGPL-3.0
Fla Ascend Performancefla-org/flash-linear-attention5.8k—~6.3kAutomated safety check: PassMIT
Deepsec Documentation Guidevercel-labs/deepsec8.1k—~956Automated safety check: PassApache-2.0
Skill Scannergetsentry/skills1k4 repos~2.5kAutomated safety check: WarnApache-2.0
Serenity Aleabitoreddityan-labs/serenity-aleabitoreddit4801 repos~3.3kAutomated safety check: PassNone
Security Alert Triageelastic/agent-skills5921 repos~3.5kAutomated safety check: NotesApache-2.0

Similar skills

  • Fla Ascend Performance

    fla-org/flash-linear-attention

    Guidelines for Ascend NPU kernel / Triton-Ascend backend performance work in the FLA repo.

    5.8k GitHub stars~6.3k tokensUpdated today
    SecurityAuto-check passed
  • Deepsec Documentation Guide

    vercel-labs/deepsec

    Official

    Points the agent at deepsec's own docs to answer questions about initializing, configuring, resuming, scanning with and extending the vulnerability scanner.

    8.1k GitHub stars~956 tokensUpdated 8 days ago
    SecurityAuto-check passed
  • Skill Scanner

    getsentry/skills

    Official

    Scan agent skills for security issues. An agent skill from getsentry/skills.

    1k GitHub starsUsed in 4 repos~2.5k tokens
    SecurityAuto-check: warnings
  • Serenity Aleabitoreddit

    yan-labs/serenity-aleabitoreddit

    Apply trader Serenity's (@aleabitoreddit) AI/semiconductor supply-chain analytical lens to US-stock ideas and market judgment.

    480 GitHub starsUsed in 1 repo~3.3k tokens
    SecurityAuto-check passed
  • Security Alert Triage

    elastic/agent-skills

    Official

    Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.

    592 GitHub starsUsed in 1 repo~3.5k tokens
    SecurityAuto-check: notes
  • Shiro Attack CLI

    SummerSec/ShiroAttack2

    当用户要求利用、检测或测试 Apache Shiro rememberMe 反序列化漏洞 (Shiro-550, CVE-2016-4437) 时使用。触发词包括 "Shiro"、"rememberMe"、"shiro attack"、"CVE-2016-4437"、"Shiro-550"、"爆破 Shiro key"、"利用 Shiro"、"Shiro…

    2.6k GitHub stars~945 tokensUpdated 4 mo ago
    SecurityAuto-check passed

More from SAP/project-foxhound

All 10 skills in this repo
  • Accessibility Frontend Review

    SAP/project-foxhound

    Official

    Performs an accessibility code review of a local diff or Phabricator revision in the style of the Firefox accessibility team.

    180 GitHub starsUsed in 2 repos~3.2k tokens
    Auto-check passed
  • JS Perf Investigation

    SAP/project-foxhound

    Official

    Structured performance opportunity investigation for SpiderMonkey (the Firefox JavaScript engine).

    180 GitHub starsUsed in 2 repos~4.1k tokens
    Auto-check passed
  • Specmap

    SAP/project-foxhound

    Official

    Map relationships between a web spec section, its Firefox implementation code, and Web Platform Tests.

    180 GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check passed
  • Stmo

    SAP/project-foxhound

    Official

    Manage Redash queries and dashboards on Mozilla's STMO (sql.telemetry.mozilla.org) using stmo-cli.

    180 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • Android New Module

    SAP/project-foxhound

    Official

    Guide for creating new Android gradle modules in the android-components project.

    180 GitHub starsUsed in 2 repos~1.8k tokens
    Auto-check passed
  • Profiler Analysis

    SAP/project-foxhound

    Official

    Analyze Firefox performance profiles using the profiler-cli CLI tool.

    180 GitHub starsUsed in 2 repos~1.1k tokens
    Auto-check passed

Categories

Questions about Bug Filing

What does Bug Filing do?

File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description. Bug Filing is an agent skill from SAP/project-foxhound, published by the product's own GitHub organization. File a Bugzilla bug for Firefox/Gecko work, or draft a bug summary and description.

When should I use Bug Filing?

Bug Filing fits situations like: the user asks to file a bug; wants a bug summary/description for a change; needs to report a defect/enhancement/task.

How do I install Bug Filing in Claude Code?

Run `npx skills add SAP/project-foxhound --skill bug-filing -a claude-code`. Or copy the skill folder (.agents/skills/bug-filing in SAP/project-foxhound) into .claude/skills/bug-filing in your project. Claude Code loads it when a task matches its description.

How do I install Bug Filing in Codex?

Run `npx skills add SAP/project-foxhound --skill bug-filing -a codex`. Or copy the skill folder (.agents/skills/bug-filing in SAP/project-foxhound) into .agents/skills/bug-filing in your project. Codex loads it when a task matches its description.

Can I use Bug Filing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SAP/project-foxhound --skill bug-filing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bug-filing, .gemini/skills/bug-filing, .github/skills/bug-filing and .opencode/skills/bug-filing in your project.

What does Bug Filing need to run?

Going by SKILL.md and its folder, Bug Filing needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Bash(./mach file-info:*), Bash(python3 .agents/skills/bug-filing/file-bug.py:*), Bash(python3 .claude/skills/bug-filing/file-bug.py:*).

Does Bug Filing access the network?

SKILL.md names 1 domain. In commands or code: tests.firefox.dev; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Bug Filing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bug Filing use?

Bug Filing is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bug Filing use?

About 828 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bug Filing?

Skills that share tags, products or a category with Bug Filing: Fla Ascend Performance (fla-org/flash-linear-attention, 5.8k stars), Deepsec Documentation Guide (vercel-labs/deepsec, 8.1k stars), Skill Scanner (getsentry/skills, 1k stars) and Serenity Aleabitoreddit (yan-labs/serenity-aleabitoreddit, 480 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bug Filing?

SAP (a GitHub organization, an official publisher) maintains it in SAP/project-foxhound, which has 180 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.

Source: SAP/project-foxhound on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.