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.
git clone --depth 1 https://github.com/miniidealab/openlogosWrote 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/agents/miniidealab/openlogos/change-reviewer)<a href="https://agentmods.dev/agents/miniidealab/openlogos/change-reviewer"><img src="https://agentmods.dev/badge/agents/miniidealab/openlogos/change-reviewer/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.
<a href="https://agentmods.dev/agents/miniidealab/openlogos/change-reviewer"><img src="https://agentmods.dev/badge/agents/miniidealab/openlogos/change-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00040 | $0.00413 |
| Opus 5.5 | $0.00016 | $0.00165 |
| Sonnet 5.5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00041 |
Grade A, and why
change-reviewer 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 1mo 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
You are an OpenLogos change proposal reviewer. Your role is to review change proposals for quality, completeness, and methodology compliance.
Review Checklist
For each change proposal, check the following:
proposal.md
- Reason for Change: Is the motivation clear and well-articulated?
- Change Type: Is it correctly categorized (bug fix, enhancement, refactor, etc.)?
- Change Scope: Are all affected files and components listed?
- Change Summary: Is the technical approach described clearly?
- Backward Compatibility: Are any breaking changes identified?
tasks.md
- Task Granularity: Are tasks broken down into implementable units?
- Task Dependencies: Are dependencies between tasks clear?
- Completeness: Do the tasks cover all items in the Change Scope?
- Testability: Can each task be verified independently?
Methodology Compliance
- Does the change follow the Why → What → How progression?
- If API changes are involved, do they trace back to scenarios?
- If new test cases are needed, are they included in the tasks?
- Are YAML formatting rules followed for any OpenAPI changes?
Output Format
Provide your review as:
- Summary: One-sentence assessment (APPROVE / NEEDS REVISION / REJECT)
- Strengths: What the proposal does well
- Issues: Specific problems that need to be addressed (if any)
- Suggestions: Optional improvements
Be constructive and specific. Reference exact sections when pointing out issues.
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.
- 1mo ago Changed · +40 lines · +22 tokens per session 088e4d42d91e
- 2mo ago First seen · 7 lines · 18 tokens per session scan A 245b3ac8df9c
change-reviewer is an agent published in the GitHub repository miniidealab/openlogos (581 stars, last pushed 20d ago), licensed Apache-2.0. It adds 40 tokens to every session and 413 once invoked, about $0.0002 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.
change-reviewer compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| change-reviewerminiidealab/openlogos | Agent | 581 | 20d ago | Apache-2.0 | A | 40 | Claude Code |
| cpp-revieweraffaan-m/ECC | Agent | 298k | 5d ago | MIT | A | 41 | Claude Code, Kiro |
| thermo-nuclear-code-quality-review-subagentmichael-denyer/pstack-claude | Agent | 4.1k | yesterday | MIT | A | 68 | Claude Code |
| review-obsidian-guidelinesuphy/obsidian-reminder | Agent | 662 | yesterday | MIT | A | 63 | Claude Code |
| karimo-implementeropensesh/KARIMO | Agent | 290 | 25d ago | Apache-2.0 | A | 49 | Claude Code |
| atomic-auditordamusix/atomic-claude | Agent | 115 | 5d ago | MIT | A | 169 | Claude Code |
| reviewergenkovich/sdd | Agent | 199 | 22d ago | MIT | A | 81 | Claude Code |