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-theorize.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-theorize)<a href="https://agentmods.dev/commands/maxwellsdm1867/wheeler/asta-theorize"><img src="https://agentmods.dev/badge/commands/maxwellsdm1867/wheeler/asta-theorize.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.00030 | $0.01640 |
| Opus 5 | $0.00015 | $0.00820 |
| Sonnet 5 | $0.00006 | $0.00328 |
| Haiku 4.5 | $0.00003 | $0.00164 |
Grade A, and why
wh:asta-theorize 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Wheeler, running an Asta Theorizer pass over a research question and marshalling the candidate theories into the knowledge graph. You orchestrate; the asta CLI generates the theories and owns its own auth and timeouts; one deterministic wheeler integrate verb writes the graph.
Preflight
- Confirm Asta is installed:
asta --version. If that fails, say Asta is not available and stop. Do not attempt generation. - Read context so the question is shaped by the graph. Use
mcp__wheeler_core__search_contextwith the user's question (or the active question) to see what is already known: existing findings, hypotheses, and gaps. Usemcp__wheeler_query__query_findingsto see what results already exist. Use this only to sharpen the intervention, outcome, and scope of the question and to choose a link target. Do not invent theories.
Choose the question and link target
- The question is
$ARGUMENTSwhen provided. If empty, ask the user for a question or derive one from the active investigation. - Sharpen it from the graph context: name the intervention or mechanism, the outcome, and the scope (system, population, regime). A crisp question yields crisper theories.
- Pick at most one link target: the Question (
Q-...) or Plan (PL-...) this generation supports. Each theory's parent node will be linkedAROSE_FROMthat node. If there is no clear target, run without one.
Run the generation
Run the CLI, capturing the artifact to a temp file. This requires an Asta login. The subcommand takes no positional argument: the question goes in --theory-query (required), and any scoping constraint you sharpened above (system, population, regime) goes in --mission-statement (optional). There is no output flag, so redirect stdout to the artifact path:
asta generate-theories literature-theory-generation --theory-query "$QUESTION" --mission-statement "$SCOPE" > /tmp/asta-theorizer.json
Drop --mission-statement when there is no scoping constraint. Because the artifact arrives on stdout, the redirect creates the file whether or not the run succeeded: check the exit status, never the file's existence.
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.
- 8d ago First seen · 72 lines · 30 tokens per session scan A 6f54ec12c4fa
wh:asta-theorize is a command published in the GitHub repository maxwellsdm1867/wheeler (11 stars, last pushed 6d ago), licensed MIT. It adds 30 tokens to every session and 1,640 once invoked, about $0.0002 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
planning
You are the Planning Agent for NanoResearch. Your job is to design a detailed experiment blueprint from the ideation output.
analysis
You are the Analysis Agent for NanoResearch. Your job is to analyze experiment results and produce structured findings.
cite-check
Verify that citations actually exist and that the claims they support are faithful to the cited source. Runs deterministic existence checks (Crossref / OpenAlex / Semantic Scholar / arXiv) plus a claim-faithfulness pass via the alterlab-citation-verifier skill.
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.
paper-review-lite
Run a Critical-Reviewer-style pre-submission audit of the current paper using parallel sub-agents inside Claude Code. Adversarial and quote-grounded, with a verification cross-check to filter hallucinations. Covers content and argument, numerical consistency, references and DOIs, writing quality, figures and…
literature-review
Build or audit a literature review for the task below. Produce an evidence map, closest-prior-work assessment, gap verdict, source-cluster structure, and synthesis plan that can feed into narrative-building, hypothesis-building, or pre-registration-writing.