Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ashlrai/ashlr-plugin/plugin install ashlrWrote 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/ashlrai/ashlr-plugin/ashlr-orchestrate-status)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-orchestrate-status"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-orchestrate-status.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.00029 | $0.00736 |
| Opus 5 | $0.00015 | $0.00368 |
| Sonnet 5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
ashlr-orchestrate-status 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description
/ashlr-orchestrate-status reads the local orchestration result cache under ~/.ashlr/orchestrations/ and renders either a flat table of recent runs (default) or a per-node tree for a single graph. Each /ashlr-orchestrate invocation persists a result.json here best-effort, so this command works fully offline with no network or telemetry side-effects.
The cache is pruned to the 50 most-recent runs on every write, so disk usage stays bounded without manual cleanup.
Usage examples
# Show a table of the 10 most-recent runs
/ashlr-orchestrate-status
# Drill into a single run by graph-id
/ashlr-orchestrate-status g-abc12345
# Dump raw JSON (list mode or detail mode) for piping to jq
/ashlr-orchestrate-status --json
/ashlr-orchestrate-status --json g-abc12345
# Show more than 10 rows
/ashlr-orchestrate-status --last 25
Output
List mode prints a fixed-width table with one row per run, newest first:
graph-id ok startedAt tokens goal
------------------------ ------ ---------------------- -------- ------------------------
g-1727-mfa ok 2026-05-22T18:04:12.0… 24000 refactor the auth flow t…
g-1727-retry fail 2026-05-22T17:11:03.4… 16000 harden retry logic in se…
g-1727-docs ok 2026-05-22T15:48:51.9… 12000 document the orchestrat…
3 of 3 runs shown
Detail mode renders a per-node tree:
Run g-1727-mfa
goal: refactor the auth flow to add MFA
tier: pro
ok: true
startedAt: 2026-05-22T18:04:12.013Z
finishedAt: 2026-05-22T18:04:13.821Z
duration: 1808ms
tokens: 24000
nodes:
├─ [ok] node-explore (refactorer, 412ms, 8000 tokens)
├─ [ok] node-implement (refactorer, 1083ms, 8000 tokens)
└─ [ok] node-verify (test-writer, 313ms, 8000 tokens)
When the cache is empty: No orchestration runs yet — use /ashlr-orchestrate to start. (exit 0).
When an id is given but not found: No run found with id <graph-id> (exit 1).
Malformed result.json files are skipped with a one-line stderr warning.
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 · 73 lines · 29 tokens per session scan A 321e658469b6
ashlr-orchestrate-status is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed 6d ago), licensed MIT. It adds 29 tokens to every session and 736 once invoked, about $0.0001 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
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
rp-build-cli
Build with rp-cli context builder → chat → implement.
specsync-create-spec
Create a new spec-sync module spec.
nimbus-embedding-routing
Hybrid 384/1536-dim embedding routing (Phase 5 T6 PR 3): PROSEHEAVYTYPES, EMBEDDINGDIMLOCAL/EMBEDDINGDIMOPENAI, the RoutingEmbeddingPipeline wrapper, dual-table search (vecitems384 + vecitems1536 via vectorSearchChunksDual), the V30 migration (1536-dim table + dim-aware delete triggers), the nimbus index reembed CLI +…
piratebao-help
Show PirateBao command card.