Skip to main content
The value report is the Org Scan report that Mnemom runs for you. It reads your GitHub pull requests and, if you connect it, your Anthropic usage. It then shows up to five problems, what each one is based on, and the Mnemom capability that addresses it.
Mnemom switches the value report on one org at a time. It is not available to customer orgs yet. Until it is on for your org, the report you get is the email from the command-line scan. See Run Org Scan yourself.

What you are asked for

Two things, both in plain terms:
  • Install the GitHub Scan app on the repositories you want scanned. It is read-only. It asks for repository metadata, pull requests and checks. It does not ask for your code.
  • Connect your Anthropic usage, or type a monthly figure. Connecting lets the report measure your API spend. With no API usage, you can type your approximate monthly AI spend instead. Both are optional. Without either, the report has no cost row.
An owner or admin of the org starts the scan, and Org Scan must be switched on for the org. See Get Org Scan switched on.

The period it covers

The report covers the 13 most recent full weeks, in UTC, each starting on a Monday. The week in progress is never included. Trends compare the first four weeks of that window with the last four. The top of the report shows:

How to read a row

The report has at most one row for each of five themes: cost, velocity, rework, follow-up and time. A theme with nothing to show has no row. Each row has:
  • A severity: high, medium or watch.
  • A headline: one sentence naming the problem.
  • A figure: the number behind the headline, marked measured or estimate.
  • Evidence: the counts the figure comes from, each with its label.
  • A target, on some rows. See Targets.
  • A recommended fix: a Mnemom capability, what it does, the command that starts it, and a link to its docs.
Rows are sorted by severity, high first. Two rows with the same severity keep the theme order above. The first row is marked as the largest.

Measured and estimate

Every line that holds a dollar amount, a percentage or a number of hours says whether it is measured or an estimate.
  • Measured figures are counted from GitHub or read from your Anthropic usage reports.
  • Estimates are worked out from those counts. A yearly cost appears only on the cost row, as an estimate at the pace of the last four weeks.
  • A range is written “between X% and Y%” and is a 95% confidence interval.
  • AI-assisted counts are a floor, written “at least”. The scan only knows a pull request is AI-assisted when it carries a mark of an AI tool, so some AI-assisted work is counted as other work.

Minimum sample

A figure for the whole org needs at least 20 pull requests. The one exception is the count of merges with no approving review when every merged pull request was read. A comparison between AI-assisted work and other work needs at least 20 in each group. Below that, the report does not show the figure. A median time to merge is shown only for a group with at least 20 merged pull requests.

The review figures

Two figures come from pull-request reviews read on a sample. See What the scan reads.
  • Sent back for changes. A floor, written “at least … sent back for changes on GitHub before merging”. The scan does not see changes asked for outside GitHub.
  • Merged with no approving review. Written “merged with no approving review from a person on GitHub”. An approval from a bot or app does not count. When every merged pull request was read, it is a count. Otherwise it is a share with a 95% range, “measured on a sample of N”.
If any review read fails, the report leaves out both figures and keeps the rest unchanged.

A monthly figure you typed

With no Anthropic usage connected, a cost row can come from the monthly figure you typed. It is shown under the label Reported monthly and the headline says the team reported it. It is your figure, not a measurement, and the report marks it as an estimate.

Targets

A target is a direction for a row, not a promise. Every target is labelled as an estimate and has no dollar amount. There are two kinds:
  • The published target. Only on cost rows where spend is rising: long sessions cost 20% to 35% less than stock Claude Code in Mnemom datasets. This is an estimate. Its source is Agent savings.
  • Your own baseline. Some rows compare you with yourself, and the line ends with Basis: and what it was drawn from. For example, the AI-assisted sent-back share is compared with your own rate for work with no AI mark.
Targets appear on these rows only: spend_rising_fast and spend_rising (the published target), and ai_up_output_flat, repos_not_ready, ai_sent_back_more, other_work_waits_longer and reverts_present (your own baseline). See Which rule picks each row.

Which rule picks each row

Rule table 2026-11.2 has 14 rules. In each theme, the first rule that matches picks the row. Each theme has one fix, with one exception. A follow-up row picked by merged_without_approval gets its own fix, because that row is about work nothing on GitHub checked. Every fix links to Mnemom Agent.

What the scan reads and does not cover

From GitHub, through the Scan app, the scan reads pull-request metadata: size, check results, the merge day, revert markers, marks of AI tools, and review state on a sample. It never reads code, diffs or file names, and it does not keep who wrote or reviewed anything. The details are in What the scan reads. From Anthropic, when you connect it, the scan reads your usage and cost reports. The report does not cover:
  • Subscription seats, such as Claude Team or Enterprise plans. Measured spend is Anthropic API usage only.
  • Other AI providers. Their spend is not read.
  • AI-assisted work with no mark of an AI tool. It is counted as other work.
  • The quality of your code. The scan does not read it.

What Mnemom keeps

Mnemom holds the signed report on the scan’s run record for 24 hours after the scan finishes, so the Org Scan page can show it again in that time. After 24 hours the run record no longer serves it. Past that, the report lives only in any export you save. On a Mnemom host that keeps reports in its own storage, the signed report is kept there for 30 days after the scan finishes instead, and the Org Scan page lists it and shows when it will be deleted. An owner or admin of the org can delete a finished scan’s report before it is deleted with DELETE /v1/orgs/{org_id}/scan/runs/{run_id}. It answers 204 and records an audit entry with the org id and scan id. The run record stays, without the report. Before the report, the same call deletes the usage file and the run data file described below. A scan that is still queued or running answers 409 scan_run_active and nothing is deleted. A member gets 403 org_scan_role_required.

Files kept beside the report

Two files can be stored beside the report. Each is stored only on a Mnemom host that keeps reports in its own storage for 30 days, and only where Mnemom has switched that file on. Each is named from your org id and the scan id only, and is kept at every share level, none included. The GitHub run data file holds the counts the report was built from.
  • What it holds: counts for each repository and one row for each merged pull request, with the week, the hours to merge to one decimal place, lines added and deleted, files changed, the check result, whether it was reverted, the names of AI tools it marks, whether it was too large to read and, for a sampled pull request, the two yes or no review facts. For each repository, the day each week was read from GitHub. The review sample’s counts. The spend figures behind the cost row: the monthly AI spend you typed, in cents, or, from a pasted Admin key, the dollars over the period, the token total, the share of tokens in long sessions and the 13 weekly dollar totals. Your org id, the scan id, the window, the rule table, the report version, whether the GitHub read was complete, why it stopped if it did not, which GitHub API was used and the time the report was made. It names your repositories, as the report does.
  • What it never holds: an author, reviewer, login, email address, pull request number, title, description, branch, commit, a pull request’s exact time, a key or any credential. Spend figures per model or per day are in the usage file, not here.
  • How long it is kept: as long as the report. It is stored only after the report is stored, and a scan that fails stores none. An owner or admin of the org can download it with GET /v1/orgs/{org_id}/scan/runs/{run_id}/data while the report can be opened.
  • How to delete it early: delete the report as above. Deleting your Mnemom account deletes it for every scan you started, and deleting your org deletes everything stored for it.
  • Copies in a later scan: where Mnemom has switched on reuse of earlier weeks, a later scan of your org can copy weeks from this file into its own run data file, up to 30 days after each week was first read. Deleting this report does not delete those copies. Each copy is kept and deleted with the later scan’s report, so delete that report too.
The Anthropic usage file holds the usage the scan read with a temporary Admin key you pasted. With no pasted key, there is no usage file.
  • What it holds: for each day, model and context window, the tokens of uncached input, cache writes (1 hour and 5 minutes), cache reads and output. For each day and model, the cost in cents. The model names, the first day read and when the figures were last refreshed.
  • What it never holds: the key, a key id, a workspace, your org id, or any author, reviewer, login, email address, pull request, branch, commit or credential.
  • How long it is kept: 30 days after the scan finishes. If the scan fails, the cleanup that runs every five minutes deletes it.
  • How to delete it early: delete the report as above, which deletes this file first. Deleting your Mnemom account deletes it for every scan you started, and deleting your org deletes everything stored for it.
The storage also deletes anything older than 30 days on its own. No route reads the usage file back.

Records of a scan

At every share level, Mnemom keeps these records of a scan:
  • A run record: who started it, their role and how they signed in, the share level, the status and any failure code, the times it was created, started and finished, the GitHub numbers of the repositories (not their names), and the Anthropic Console ids you connected, if any. These are ids, not secrets. An email address you gave for the summary is cleared when the scan ends.
  • An audit entry when the scan starts: who started it, the org id, the scan id, the share level and the number of repositories.
  • An audit entry each time Mnemom issues a workload identity token for the scan to read your Anthropic usage: who started the scan, the org id and the scan id.
At share levels other than none, Mnemom also keeps:
  • A run log entry: the scan id, who ran it, the time, the share level and whether the email was delivered.
  • A send log: one entry for each email, with the recipient address and the subject line.
At every level, Mnemom’s email provider keeps its own delivery record of each email. None of these records holds a token, the report or its counts. Only the held report and the two files above do. The share levels are described in Choose what Mnemom keeps. To have Mnemom delete anything it holds about a scan, email privacy@mnemom.ai.

The email summary

When the scan finishes, the email summary lists up to five row headlines, the window and the as-of time. It links to the Org Scan page and to the method. It never names a repository. The full report, with repository names, is on the page and in your export.

Export the report

Under Export this report, there are two buttons:
  • Save data file saves mnemom-org-scan-report-YYYY-MM-DD.json. It holds the signed report.
  • Save page saves a single .html file that opens in any browser, offline. The signed data file is inside it.
Both name your repositories. Keep them as you would any internal document.

Open it again

For 24 hours after the scan finishes, or 30 days on a host that keeps reports in its own storage, the Org Scan page shows the report again, including after a reload. After that, no Mnemom link opens it. To see it again:
  • open the saved page in a browser, or
  • load the saved data file on the Verify a saved report page in your organization’s Org Scan settings. It checks the signature in your browser and sends nothing to Mnemom.
To get a fresh report, run the scan again.

Verify the signature

The saved page does not check its own signature. To check it, load the data file on the Verify a saved report page, or verify it yourself. The data file is JSON with a jws field. That is a compact JWS signed by Mnemom with Ed25519. To verify it yourself:
  1. Read the JWS header. Check that alg is EdDSA and typ is OrgScanReport/v1.
  2. Fetch the signing keys from the Mnemom API host your org uses, at /v1/.well-known/jwks.json. For example, https://api.mnemom.ai/v1/.well-known/jwks.json. Find the key whose kid matches the header. A kid that is not there means the report was signed by a different Mnemom host.
  3. Verify the signature with that key.
  4. In the payload, check that iss is https://mnemom.ai and sub is your org id. The token also carries iat (when it was signed) and exp (by default 365 days later). The Verify a saved report page does not check either time, so a saved report still verifies there after exp. Check exp yourself if your policy needs it.
  5. The report is the report claim. Its schema_version is org-scan-report/2.
The exported_at time in the data file is outside the signature. These are the same keys and steps as for an AAP attestation.