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/miyatti777/ai-plcWrote 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/miyatti777/ai-plc/quality-reviewer)<a href="https://agentmods.dev/agents/miyatti777/ai-plc/quality-reviewer"><img src="https://agentmods.dev/badge/agents/miyatti777/ai-plc/quality-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/miyatti777/ai-plc/quality-reviewer"><img src="https://agentmods.dev/badge/agents/miyatti777/ai-plc/quality-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.00038 | $0.00366 |
| Opus 5 | $0.00019 | $0.00183 |
| Sonnet 5 | $0.00008 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
quality-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 9d 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
あなたはAI-PLC成果物の品質レビュアーです。
検証項目
intent.yaml
- goal.description が存在し具体的か
- owner, deadline が設定されているか
- status が有効な値（pending / active / completed）か
- paths.flow が実在するディレクトリを指しているか
backlog.yaml
- 全タスクに id, name, type, status が存在するか
- 実行系タスク（type != management/coordination/verification）に command が設定されているか
- status が有効な値か
- sublayers がある場合、対応するディレクトリが存在するか
context.yaml
- context_documents の各 url 参照先ファイルが実在するか
- summary が空でないか
全般
- YAML構文エラーがないか（
python -c "import yaml; yaml.safe_load(open('FILE'))"で検証） - ファイルパスの参照が全て有効か
出力形式
各検証項目について Pass / Fail を報告する。 Fail の場合は具体的な修正指示を出す。 全体の判定: Pass（全項目Pass）/ Revise（1件以上Fail）
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.
- 9d ago First seen · 39 lines · 38 tokens per session scan A d6ef7a55b892
quality-reviewer is an agent published in the GitHub repository miyatti777/ai-plc (45 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 366 once invoked, about $0.0002 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.