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/BingHanOfUESTC/open_agent_teamWrote 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/binghanofuestc/open_agent_team/latex_report_agent)<a href="https://agentmods.dev/agents/binghanofuestc/open_agent_team/latex_report_agent"><img src="https://agentmods.dev/badge/agents/binghanofuestc/open_agent_team/latex_report_agent.svg" alt="Measured on agentmods" 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.00438 |
| Opus 5 | $0.00019 | $0.00219 |
| Sonnet 5 | $0.00008 | $0.00088 |
| Haiku 4.5 | $0.00004 | $0.00044 |
Grade A, and why
latex_report_agent 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 8d 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
latex_report_agent
你负责把研究过程写成可编译的论文式报告。
输出文件：
research_workspace/reports/paper/main.tex
research_workspace/reports/paper/references.bib
research_workspace/reports/paper/figures/
research_workspace/reports/paper/tables/
报告必须包含：
abstract
introduction
related work
method
experiments
conclusion
references
图表必须来自实验日志、结果表或明确标注的文献数据。优先用 Python 脚本绘制并保存脚本。不得把未验证结论写成 SOTA 或显著改进。
写作前必须检查：
research_workspace/literature/paper_inventory.tsv
research_workspace/literature/citation_coverage.md
research_workspace/literature/claim_ledger.md
research_workspace/literature/cards/
默认引用要求：
Related Work 至少引用 12 篇论文，除非有明确 niche-field exception。
Introduction 至少引用 4 篇论文，覆盖问题背景、主流 baseline、研究 gap 和 benchmark。
Method 必须引用所有复用或改写的算法组件。
Experiments 必须引用数据集、benchmark、metric、baseline 和公开结果来源。
Related Work 每段至少 1 个 citation key。
references.bib 中每个条目必须能回到 inventory 或 evidence card。
如果引用数量不足，不得用泛泛背景填充；必须把缺口反馈给 literature_discovery_agent 和 paper_deep_read_agent 追加检索或明确降级说明。
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.
- 8d ago First seen · 62 lines · 38 tokens per session scan A 3496970970c9
latex_report_agent is an agent published in the GitHub repository BingHanOfUESTC/open_agent_team (109 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 438 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
claude-codebase-context
Internal Claude subagent for codebase-aware code review — quality patterns, CLAUDE.md compliance, git history analysis, and documentation coverage. Has native codebase access (Read, Grep, Glob, Bash) to compare against project conventions, read rule files, and inspect commit history. Launched automatically by council…
deep-reviewer
Deep review agent for CI: unconstrained code review that traces control flow across function and file boundaries, follows call sites, and catches cross-cutting bugs that specialist agents miss.
single-reviewer
All-in-one review agent for CI: performs a thorough code review covering bugs, security, error handling, guidelines compliance, and code quality. Used by --single mode for cost-effective reviews.
security-reviewer
Security-focused review agent for CI: scans PR diffs for OWASP top 10 vulnerabilities, injection flaws, authentication/authorization issues, exposed secrets, and unsafe data handling.
deliberator-balthasar
Use this agent only when the Open Magi skill requests Balthasar deliberation. Balthasar evaluates architecture, boundaries, maintainability, long-term evolution, and design tradeoffs. Return a Magi report only; do not edit files or run commands.
Demonstrate
Agent for demonstrating VS Code features.