sota-report

sota-report is a command for Claude Code from martinholovsky/SOTA-skills. It costs 49 tokens per session (2,679 once invoked), scanned A, original, CC-BY-4.0.

A command for writing an end-of-session report about guidance that was missing, wrong, ineffective, or correctly applied. It uses the current session history as its source.

In plain words
What is it for?
Use it at the end of a coding-agent session to document failures, omissions, and successful guidance.
Why use it?
It gives teams a way to record what went wrong or worked while the details are still available.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sota-skills plugin — 43 skills, 5 commands, 3 hooks shipped together

Good fit Use it at the end of a coding-agent session to document failures, omissions, and successful guidance.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/martinholovsky/sota-skills/sota-report
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/martinholovsky/SOTA-skills

Made for: Claude Code.

Or install sota-skills, the plugin that ships this one along with the rest of its 43 skills, 5 commands, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sota-report

README.md
[![agentmods](https://agentmods.dev/badge/commands/martinholovsky/sota-skills/sota-report/github.svg)](https://agentmods.dev/commands/martinholovsky/sota-skills/sota-report)
Your own site
<a href="https://agentmods.dev/commands/martinholovsky/sota-skills/sota-report"><img src="https://agentmods.dev/badge/commands/martinholovsky/sota-skills/sota-report/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sota-report

Your own site · 80×15
<a href="https://agentmods.dev/commands/martinholovsky/sota-skills/sota-report"><img src="https://agentmods.dev/badge/commands/martinholovsky/sota-skills/sota-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,679 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.02679
Opus 5.5 $0.00020 $0.01072
Sonnet 5.5 $0.00010 $0.00536
Haiku 4.5 $0.00005 $0.00268

Measured 8d ago against content hash 76c14ec7ab0c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sota-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/sota-report.md · 186 lines

The source is not reproduced here

Licensed CC-BY-4.0

The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago Changed · +6 lines 76c14ec7ab0c
  2. 27d ago Changed · +2 lines 1863acc6306e
  3. 1mo ago Changed · +12 lines 16027302b31f
  4. 1mo ago First seen · 166 lines · 49 tokens per session scan A dab45ed48642

Subscribe to this mod's changes

sota-report is a command published in the GitHub repository martinholovsky/SOTA-skills (23 stars, last pushed today), licensed CC-BY-4.0. It adds 49 tokens to every session and 2,679 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-15.