Skip to content

Instantly share code, notes, and snippets.

@gcavalcante8808
Created June 9, 2026 01:01
Show Gist options
  • Select an option

  • Save gcavalcante8808/e5b4173dab2d66fd8c9c18d2e04d4742 to your computer and use it in GitHub Desktop.

Select an option

Save gcavalcante8808/e5b4173dab2d66fd8c9c18d2e04d4742 to your computer and use it in GitHub Desktop.
Mellum 2 sidecar tool test prompt

You are auditing the sidecar codebase. Complete all five tasks. Use the exact output format below.

The sidecar codebase root is: /workspace/sidecar

Task 1 — Discovery (glob): Find all .rs files under /workspace/sidecar/sidecar-core/src/adapters. List each path, one per line.

Task 2 — Pattern search (grep): Find every occurrence of `call_tool` across the codebase. For each match report: file path, line number, exact line.

Task 3 — Code reading (read): Find and read otel_probe.rs. List every tool metric counter field in OpenTelemetryProbe (name and type). In one sentence, explain which observation records guard blocks.

Task 4 — Shell (bash): Run git -C /workspace/sidecar log --oneline -5 and report the output verbatim.

Task 5 — Write (write): Use the write tool to write a file called /tmp/0cdeadde-637a-4c21-ac05-d06d4181d21c.txt, with your complete responses for Tasks 1-4 using the headers below. Do not add any other content. If the file exists, remove it before creating a new one.

Validation:

  • After writing the file, confirm the write succeeded and that the file exists.
  • Report any tool errors or guard blocks encountered while solving Tasks 1-5.
  • Include the benchmark duration and TPS values if they were visible in the terminal metrics.
  • Everytime that you use a tool, explain why you used it and explain the returned results;

Output format — use exactly these headers:

Task 1

Task 2

Task 3

Task 4

Validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment