openlogos-next

A command that gives the next-step status for an OpenLogos project. OpenLogos appears to be a project with phases described in an AGENTS.md file.

In plain words
What is it for?
It is for running openlogos status and using the project's phase information to recommend the next action or prompt.
Why use it?
It provides guidance when there is no separate next command and helps users understand what to do next.

Command

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.

agentmods
npx agentmods add commands/miniidealab/openlogos/openlogos-next
Clone the repo
git clone --depth 1 https://github.com/miniidealab/openlogos
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 80 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original 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 $0.00023 $0.00080
Opus 5 $0.00012 $0.00040
Sonnet 5 $0.00005 $0.00016
Haiku 4.5 $0.00002 $0.00008

Measured 3d ago against content hash dbca63b6556d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openlogos-next 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 3d 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.

examples/money-log/.opencode/commands/openlogos-next.md · 10 lines

What it actually says

CLI 暂无独立 next 子命令,当前映射为 status:

!openlogos status

请结合 AGENTS.md 中的 Phase 检测逻辑,向用户说明下一步建议与可用提示词。

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. 3d ago First seen · 10 lines · 23 tokens per session scan A dbca63b6556d

Subscribe to this mod's changes

openlogos-next is a command published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 6d ago), licensed Apache-2.0. It adds 23 tokens to every session and 80 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-30.