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.
npx agentmods add commands/miniidealab/openlogos/archivegit clone --depth 1 https://github.com/miniidealab/openlogosWhat 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 | $0.00009 | $0.00269 |
| Opus 5 | $0.00005 | $0.00134 |
| Sonnet 5 | $0.00002 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
archive 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 2d 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.
What it actually says
This slash command is treated as explicit human authorization to run openlogos archive $ARGUMENTS.
Archive the completed change proposal: "$ARGUMENTS"
- If
$ARGUMENTSis empty, ask the user to provide the change slug (e.g.,/openlogos:archive my-change). - Before running, inform the user:
- Prerequisite:
openlogos verifymust have passed (PASS) before archiving - Archiving will move
logos/changes/$ARGUMENTS/tologos/changes/archive/ - If the active guard points to this proposal, it will be removed
- This action is irreversible
- Prerequisite:
- Run
openlogos archive $ARGUMENTSin the project root directory. - If the
openlogosCLI is not found, tell the user to install it:npm install -g @miniidealab/openlogos - After archiving, inform the user that the change proposal has been moved to
logos/changes/archive/and is now complete.
Note: openlogos archive is a human confirmation point. AI must not execute it without explicit user authorization. This slash command itself constitutes that authorization.
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.
- 2d ago First seen · 23 lines · 9 tokens per session scan A e789606a8823
archive is a command published in the GitHub repository miniidealab/openlogos (71 stars, last pushed 5d ago), licensed Apache-2.0. It adds 9 tokens to every session and 269 once invoked, about $0.0000 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.