DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to prepare a redacted Healthcheck summary to review with Agent Measure

Create a local summary file from a check report, inspect it, and validate it before choosing to send it.

  • Money
  • Intermediate
  • 15 minutes
  • From the README
  • Claude Code
  • Codex

Credentials. The full report.json and raw logs can contain sensitive session content, so send only the reviewed summary.json when a summary is requested.

Who it is forA developer who wants outside help with one local anomaly and needs to share only a summary, not the full logs.

The problemSending a full report or raw logs exposes more data than the question needs, but the team still needs a file that is valid and easy to inspect.

The outcomeA summary.json file written on the local machine that has been inspected and validated, ready for a decision about sharing.

What you need first

  • Python 3.9 or newer and pip
  • A terminal on macOS, Linux or Windows
  • A vendor billing export as CSV for the recount use case, or local Codex or Claude Code session logs for the log use cases
  • Permission to read the session logs or export files you point the tool at

Steps

  1. Run pip install agentmeasure to install the CLI.
  2. Run agentmeasure check --json report.json to write the full report locally.
  3. Run agentmeasure share report.json --out summary.json to write the summary on your machine.
  4. Open summary.json and inspect it line by line before you decide to send anything.
  5. Run agentmeasure validate summary.json to confirm the file is valid.

Prompt for your agent

Using the AgentMeasure repo, run `agentmeasure check --json report.json`, then `agentmeasure share report.json --out summary.json`, then `agentmeasure validate summary.json`. Report whether validation passed and list the fields in summary.json. Verify that no upload happened and that report.json was not attached to any message.

Caveat. Paid Healthcheck Diagnosis is a separate $10 service with its own scope, input requirements and refund terms on the service page, and a summary does not guarantee a root cause.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page