Borrowing it
Nothing to install: this file belongs to maxwellsdm1867/wheeler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/maxwellsdm1867/wheeler/main/.claude/commands/wh/asta-report.mdgit clone --depth 1 https://github.com/maxwellsdm1867/wheelerWrote 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.
[](https://agentmods.dev/commands/maxwellsdm1867/wheeler/asta-report)<a href="https://agentmods.dev/commands/maxwellsdm1867/wheeler/asta-report"><img src="https://agentmods.dev/badge/commands/maxwellsdm1867/wheeler/asta-report.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00050 | $0.01734 |
| Opus 5 | $0.00025 | $0.00867 |
| Sonnet 5 | $0.00010 | $0.00347 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
wh:asta-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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Wheeler, producing an Asta Literature Report (a written, multi-paper literature review) and marshalling it into the knowledge graph. The deliverable is a MARKDOWN document, not a single JSON artifact: you orchestrate asta literature find (and asta papers) for evidence, SYNTHESIZE the review yourself, then one deterministic wheeler integrate verb writes the report Document plus its cited papers into the graph with provenance.
Unlike the other Asta acts (one CLI call, one JSON -o artifact), this act writes a markdown report and ingests THAT. The asta CLI owns its own auth and timeouts; a failed search writes nothing.
Preflight
- Confirm Asta is authenticated:
asta auth status. If that fails, say Asta is not available and stop. Do not attempt the run. - Read context so the review is shaped by the graph. Use
mcp__wheeler_core__search_contextwith the topic (or the active question),mcp__wheeler_query__query_papersfor papers already recorded, andmcp__wheeler_query__query_open_questionsfor the question this review answers. Use this only to sharpen the topic and pick a link target. Do not invent findings. Do not do the scientist's thinking.
Choose the topic and link target
- The topic is
$ARGUMENTSwhen provided. If empty, ask the user or derive one from the active investigation. - Pick at most one link target: the Question (
Q-...) or Plan (PL-...) this review serves. If there is no clear target, run without one.
Gather evidence
Run the paper finder, writing its results to a temp file (this JSON also enriches each cited paper's metadata at ingest):
asta literature find "$TOPIC" -o /tmp/find.json
Supplement with targeted asta papers search / asta papers get / asta papers citations calls as needed. If asta literature find exits non-zero (including a login or auth failure), FIRST record the failed attempt so it is not silently lost (the failsafe: the external job is an Execution, and a failed one must be visible, not absent):
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.
- 6d ago First seen · 91 lines · 50 tokens per session scan A 4051ec9e7267
wh:asta-report is a command published in the GitHub repository maxwellsdm1867/wheeler (11 stars, last pushed 4d ago), licensed MIT. It adds 50 tokens to every session and 1,734 once invoked, about $0.0003 per session on Opus 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-08-31.
Other commands, from other repositories
board
Личный совет директоров (Consilium) — сборка доски, статус, заседание. Использование — /board.
research
Deep research on Claude models — full multi-agent loop, plan-only, or resume a run. Persists cited evidence to runs/ /.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
design
CPS(Context-Problem-Solution) 프레임워크로 Design 문서를 작성한다.
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).