A command that creates an OpenLogos change proposal for a named modification. The proposal stores the reason, scope, tasks, and detailed change notes in a project folder.

Use it to start a proposal, fill in its proposal and task files, request approval, then continue through implementation, merge, and archiving.

It gives a planned change a clear place to record what will be done, so implementation and later review are easier to track.

change — Command for Claude Code by miniidealab/openlogos

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/miniidealab/openlogos

Made for: Claude Code.

Or install openlogos, the plugin that ships this one along with the rest of its 10 commands, 1 agent.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/miniidealab/openlogos/change/github.svg)](https://agentmods.dev/commands/miniidealab/openlogos/change)

Your own site

<a href="https://agentmods.dev/commands/miniidealab/openlogos/change"><img src="https://agentmods.dev/badge/commands/miniidealab/openlogos/change/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/miniidealab/openlogos/change"><img src="https://agentmods.dev/badge/commands/miniidealab/openlogos/change.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 274 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.00274
Opus 5.5	$0.00005	$0.00110
Sonnet 5.5	$0.00003	$0.00055
Haiku 4.5	$0.00001	$0.00027

Measured 2mo ago against content hash bb0cc91c550a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

change 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 2mo 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.

logos/changes/archive/20260829-2333-release-0-14-1-local/deployment-artifacts-20260830T0554Z/candidate-unpack/package/claude-plugin-template/commands/change.md · 20 lines

What it actually says

Create a new OpenLogos change proposal with the slug provided as argument: "$ARGUMENTS"

If $ARGUMENTS is empty, ask the user to provide a slug (short kebab-case name describing the change).
Run openlogos change $ARGUMENTS in the project root directory.
If openlogos CLI is not found, create the change proposal manually:
- Create directory logos/changes/$ARGUMENTS/
- Create logos/changes/$ARGUMENTS/proposal.md with the standard template
- Create logos/changes/$ARGUMENTS/tasks.md with the standard template
- Create logos/changes/$ARGUMENTS/deltas/ directory
Tell the user the proposal was created and suggest next steps:
- Fill in proposal.md with the change reason, scope, and summary
- Fill in tasks.md with the implementation tasks
- After approval, implement the changes
- When ready to merge, explicitly request /openlogos:merge $ARGUMENTS to generate merge instructions
- After reviewing the merge, explicitly request /openlogos:archive $ARGUMENTS to archive the proposal

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.

2mo ago First seen · 20 lines · 13 tokens per session scan A bb0cc91c550a

Subscribe to this mod's changes

change is a command published in the GitHub repository miniidealab/openlogos (581 stars, last pushed 20d ago), licensed Apache-2.0. It adds 13 tokens to every session and 274 once invoked, about $0.0001 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-08-30.

Planning

change next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
changeminiidealab/openlogos	Command	581	20d ago	Apache-2.0	A	13	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code