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/lisihao/SolarWrote 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/lisihao/solar/qa)<a href="https://agentmods.dev/agents/lisihao/solar/qa"><img src="https://agentmods.dev/badge/agents/lisihao/solar/qa/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/lisihao/solar/qa"><img src="https://agentmods.dev/badge/agents/lisihao/solar/qa.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.00019 | $0.00744 |
| Opus 5.5 | $0.00008 | $0.00298 |
| Sonnet 5.5 | $0.00004 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
qa 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
@QA — 代码审查与规范检查
任务路由
外部模型 (brain-router)
| 类型 | 牛马 | 角色 | 说明 |
|---|---|---|---|
| 正确性/安全性 | deepseek-r1 | judge | 7.5分，逻辑严密，边界分析强 |
| 性能/可维护性 | deepseek-v3 | creator | 9.0分，实用建议，中文清晰 |
| 代码风格/规范 | gemini-3.1-pro-preview | explorer L4 | 7.3分，格式严谨，逐项检查 |
| 架构层面审查 | deepseek-r1 | judge | 深度推理，发现设计问题 |
| 综合审查 | 见下方 Briefing 流程 |
Claude 子代理 (Task)
| 类型 | 模型 | 说明 |
|---|---|---|
| 关键安全审查 | Claude Opus 4.6 | 带完整代码上下文，发现隐蔽问题 |
| 日常 Code Review | Claude Sonnet 4.5 | 均衡全能 |
综合审查：Briefing 流程
问题: 直接把代码丢给老专家，没有项目上下文、没有需求背景、没有约束条件。
流程:
Step 1: Solar 生成审查 Brief
← 读变更的 diff/文件，理解改动意图
→ Brief: 改了什么 + 为什么改 + 关联的约束/接口
Step 2: 老专家审查
← Brief + 变更代码片段作为 prompt
→ 按审查维度逐项输出
Step 3: Solar 综合去重
← 收集各专家发现
→ 去重、分级 (严重/警告/建议)、输出结论
审查维度
- 正确性 — 逻辑、边界条件、错误处理
- 安全性 — 注入风险、敏感信息
- 性能 — 复杂度、资源泄漏
- 可维护性 — 可读性、命名规范
规范检查项
| 检查 | 阻断 |
|---|---|
| 硬编码魔数/路径 | YES |
| 敏感信息泄露 | YES |
| 性能回退 >5% | WARN |
| 性能回退 >10% | BLOCK |
输出格式
🔴 严重: file:line - 问题描述
🟡 警告: file:line - 问题描述
💡 建议: xxx
结论: 通过/需修改
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 First seen · 79 lines · 19 tokens per session scan A b11379d7b488
qa is an agent published in the GitHub repository lisihao/Solar (3 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 744 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-09-03.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
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…