Add check-proxy-tax to Tools

[600me]

Summary

• Adds check-proxy-tax to the Tools section, in alphabetical order before
  CrossHair.

What it does

check-proxy-tax is a Python CLI that sends a configurable number of
concurrent requests to one URL and classifies each response as usable or
blocked. Usable means the final status is exactly 200 and, when --marker
is supplied, the body contains that marker. 403, 429, 5xx, timeouts,
connection errors, and marker misses are blocked.

It reports usable percentage, effective cost per 1,000 usable requests, tax
multiplier over the nominal price, p50/p95 latency, bytes transferred, and
status/reason counts. --json emits a single object. Exit codes are stable:
0 all usable, 1 degraded, 2 none usable, 3 invalid arguments.

Why it fits Tools

• It turns a flaky live-endpoint dependency into a deterministic CI signal.
• The JSON object is suitable for a test assertion or pipeline artifact.
• It is a standalone Python CLI with no hosted service or account.
• Pure standard library, zero runtime dependencies, MIT licensed.
• It is an analyzer/gate, like the neighboring Tools entries, not a test
  framework.

Verification

• python3 -m unittest test_cli.py -v — 14 tests pass offline.
• python3 -m check_proxy_tax.cli --help — exits 0.
• Tested on Python 3.12; declares Python 3.8+.
• pre-commit run --all-files run in the fork before opening this PR,
  including rumdl-fmt, typos, and the dead-link check.

Disclosure

The project README links to a public benchmark page that may include affiliate
tracking and carries this disclosure verbatim:

FTC Disclosure: Benchmark links may include affiliate tracking.

No tracking or affiliate link is included in the list entry above.

Summary by Sourcery

New Features:

• Add check-proxy-tax to the Tools section in alphabetical order, describing its URL sampling and proxy-cost analysis capabilities.

[semanticdiff-com]

Review changes with  

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This documentation-only change adds check-proxy-tax to the Tools section immediately before CrossHair, describing its concurrent endpoint analysis and CI-oriented reporting capabilities.

File-Level Changes

Change	Details	Files
Adds the standalone check-proxy-tax CLI to the Tools catalog in alphabetical order.	Links to the project repository. Describes concurrent URL sampling and usable-response classification. Highlights latency, cost, and response-rate reporting.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-code-review]

Code Review by Qodo

Sorry, something went wrong

We weren't able to complete the code review on our side. Please try again manually by commenting /agentic_review on this PR.

[qodo-code-review]

PR Summary by Qodo

List check-proxy-tax in the Tools section

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Adds check-proxy-tax to the Tools list before CrossHair.
• Describes its concurrent URL sampling and usable-response, latency, and effective-cost reporting.

High-Level Assessment

A concise entry in the existing Tools list is appropriate; no architectural alternative is warranted for a documentation-only addition.

Files changed (1) +1 / -0

Documentation (1) +1 / -0

README.mdAdd check-proxy-tax to Tools +1/-0

Add check-proxy-tax to Tools

• Adds a link to check-proxy-tax before CrossHair, describing its concurrent URL sampling and reported usability, latency, and effective cost. No CLI code is included in this PR.

README.md

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[llamapreview]

LlamaPReview — No blocking issues found

The only change is one correctly formatted, alphabetically placed Tools entry in README.md, whose description matches the disclosed project behavior and carries no tracking link.

Review details and evidence

LlamaPReview checks

• Read the complete PR-head file README.md.

---

Still coding alone? Open CarbonChat, a chat room right inside Codex.