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.
git clone --depth 1 https://github.com/danielsmithdevelopment/ClawQLWrote 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/rules/danielsmithdevelopment/clawql/git-pr-merge-wait-ci)<a href="https://agentmods.dev/rules/danielsmithdevelopment/clawql/git-pr-merge-wait-ci"><img src="https://agentmods.dev/badge/rules/danielsmithdevelopment/clawql/git-pr-merge-wait-ci/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/danielsmithdevelopment/clawql/git-pr-merge-wait-ci"><img src="https://agentmods.dev/badge/rules/danielsmithdevelopment/clawql/git-pr-merge-wait-ci.svg" alt="Reviewed on agentmods" width="80" 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.00253 | $0.00253 |
| Opus 5.5 | $0.00101 | $0.00101 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
git-pr-merge-wait-ci 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 1mo 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.
What it actually says
Git / PR merges — wait for CI
When merging pull requests (GitHub / gh pr merge):
- Never merge immediately after creating a PR or without verifying CI.
- Always wait for required checks to finish and pass before merging.
gh pr merge --autois not sufficient by itself: if the repository does not require specific status checks in branch protection, GitHub may merge immediately when you use--auto, before workflows finish. Do not rely on--autoalone.- Before merge, run:
gh pr checks <n> --watch --fail-fastand confirm it exits 0 (all checks finished and passed). Alternatively pollgh pr checks <n> --jsonuntil no check is pending and none failed. - Only then run
gh pr merge <n> --merge(merge-after-green). Prefer this sequence over trusting--autounless you have verified branch protection blocks merge until required checks pass.
If branch protection blocks merge until green, do not bypass it. Do not assume checks are optional.
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.
- 1mo ago First seen · 17 lines · 253 tokens per session scan A 27cb6a334e57
git-pr-merge-wait-ci is a cursor rule published in the GitHub repository danielsmithdevelopment/ClawQL (13 stars, last pushed today), licensed Apache-2.0. It adds 253 tokens to every session, about $0.0010 per session on Opus 5.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 cursor rules, from other repositories
development_workflow
Spamoor Development Workflow and Best Practices.
hook-commits
Set up pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
desktop-release-gate
Desktop app fixes must pass a local packaged build smoke test before pushing release tags or CI desktop builds.
push_rules
A project rule requiring checks before code is committed and pushed. For this Deno project, the required checks are formatting, linting, and the full test suite; new functions also need documentation and tests.
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
fusebase-flow-implementation
Fusebase Flow implementation phase rules. Use when editing source code per a locked spec.