Chromium is an open-source web browser project and the official GitHub mirror of its source code. It is used to build and maintain software for browsing the web, with documentation and code for products such as Chrome and Android WebView.
Borrowing it
Nothing to install: this file belongs to chromium/chromium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chromium/chromium/main/.gemini/commands/cr/git/pre-upload-checklist.tomlgit clone --depth 1 https://github.com/chromium/chromiumWrote 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/commands/chromium/chromium/pre-upload-checklist)<a href="https://agentmods.dev/commands/chromium/chromium/pre-upload-checklist"><img src="https://agentmods.dev/badge/commands/chromium/chromium/pre-upload-checklist.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.1 | $0.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
pre-upload-checklist 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 6d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description = """Runs a pre-upload checklist to ensure the changelist is in a high-quality, presubmit-clean state."""
prompt = """
🚀 Pre-Upload Checklist Prompt
Philosophy: The goal of this checklist is to perform a thorough manual and automated local review, ensuring the changelist is in a high-quality, presubmit-clean state before you decide whether to proceed with optional actions like building or uploading.
Part 1: Mandatory Pre-Upload Checks
1. Sync Client First, I will run gclient sync to ensure all dependencies
are up to date.
2. Identify Changed Files Next, I will identify the files that have been
modified on the current branch by running the following command:
git diff --name-only @{u}
3. Review Style Guide and Current Changes I will read the style guide at @styleguide/styleguide.md in its entirety. I will then analyze the changed files identified in the previous step to ensure they adhere to the project's coding standards. I will report any violations before proceeding.
4. Remove Debug Logging I will analyze the diff of the changed files to find
and remove any temporary logging statements, such as System.out.println or
Log.d, that may have been accidentally left in the code.
5. Add Missing Docstrings I will then analyze the full diff of the changes to identify any new or modified classes, methods, or functions that lack proper documentation. For each of these, I will:
- Write a clear and concise docstring explaining the code's purpose, parameters, and return values.
- Ensure the documentation style conforms to the relevant language-specific guidelines (e.g., JavaDoc for Java).
6. Run Presubmit Checks As a final local verification, I will run
git cl presubmit. This is a comprehensive check to ensure the changelist is
free of errors before proceeding. This step is mandatory, and I will report on
its success or failure.
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.
- 6d ago First seen · 69 lines · 0 tokens per session scan A 0e6d7bee636a
pre-upload-checklist is a command published in the GitHub repository chromium/chromium (24,735 stars, last pushed today), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 632 tokens. 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-09-02.
Other commands, from other repositories
browseros-review
You are a code review specialist. Identify genuine issues while filtering out false positives.
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.