Bounty Operator
Account

Triager simulation

See why a triager would close your report

Your model reads the draft as a triager does: fast, and looking for the reason to close it. It returns the three likeliest reasons, the sentence of yours that invites each one, and the evidence that flips it.

Simulate the triagerWhat it answers

Opens the workbench with Triager simulation selected. 1 hosted review per UTC day on your own key. No card.

ExampleExample output · invented protocol

VerdictProve first

Fastest close: impact not shown. The proof ends at the revert and the loss is narrated.

input-1/draft-report.mdRanked
Rejection reasons

The three a triager reaches first on this draft

Reason 1

Impact not shown

An attacker can steal all staked funds.

OpenThe test ends at the revert on line 58. Add an assertion on the staker’s balance after the attack.

input-3/test/Exploit.t.sol:41-58

Reason 2

Privileged precondition

After the operator raises the rate, the next claim overpays.

OpenThe rules pasted in Context exclude operator actions. Show the path without setRate, or cut the step.

input-2/StakingRewards.sol:132-137

Reason 3

Known issue

Missing section: the draft does not mention the prior audit.

AnsweredThe audit note covers access to setRate, a different root cause. Say so in the first paragraph.

input-4/audit-notes.md:112

Next

Write the balance assertion first. It answers the reason a triager reaches in the first minute.

What the simulation answers

A triager needs one sentence to close a report. The simulation writes that sentence before the triager does. The reasons reports are closed for are on the method page.

  1. The closing sentence

    The one sentence that closes this report in ten minutes, and whether your first paragraph already answers it.

  2. Three reasons, ranked

    The three likeliest rejection reasons for this draft, the likeliest first.

  3. The sentence that invites each

    Quoted from your draft. Where the trouble is a gap, the missing section is named.

  4. What flips it

    A line in the files you supplied, or the one artefact to add. Each reason is marked answered or open.

What to paste in

The rules decide half the reasons. Paste them.

  • Your draft report

    As you intend to submit it.

  • The source files it cites

    So an objection the code already answers is marked answered, with the line.

  • Programme rules and scope, in Context

    The scope list, the exclusions and the severity table. Reasons that depend on rules are judged only when the rules are supplied.

Up to 50 files, 120 KB per file, 240 KB and 20,000 lines in total. Paste, drop files, or import a repository, pull request or commit from GitHub at a pinned commit.

What comes back

Three rows, ranked, each with its way out.

  • The closing sentence, and whether your first paragraph answers it.
  • The three likeliest rejection reasons for this draft, in order.
  • For each: the sentence of yours that invites it, or the missing section.
  • For each: the evidence that flips it. A line in your files, or the one artefact to add.
  • Each marked answered or open. An objection your files already answer comes back answered, with the line.
  • One verdict: submit, rewrite-then-submit, prove-first, hold-duplicate or drop.

Questions

Does it know my programme’s rules?

It uses the rules you paste into Context: the scope list, the exclusions and the severity table. Rules it was not given are named in the review as not supplied.

Is this the platform’s own triager?

No. It is your own model, reading the draft the way a programme triager does. It runs on a draft for any platform: Immunefi, Cantina, Sherlock or HackerOne.

What do I do with an open reason?

Add the artefact the row names, or rewrite the sentence that triggers it. Then run the simulation again.

Which model runs the review?

The one you choose, on your own key: OpenRouter, Anthropic, OpenAI, Google Gemini, xAI, DeepSeek, Mistral or Groq. It runs as a hosted review: one per UTC day on Free, unlimited on Operator. From a coding agent it runs through run_review over MCP, on the same allowance.

Where do my files go?

Through our server to the model provider you choose, with your key, for that one request. The server adds the method of this profile on the way. Bounty Operator does not store your files, prompts, keys or results. The packet you download carries a SHA-256 manifest of every file reviewed.

Read your report the way the triager will

Three reasons to close it, and what answers each.

Simulate the triagerRead the method

Opens the workbench with Triager simulation selected. Free: 1 hosted review per UTC day. Operator: unlimited, US$10 per week.