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 agents/openraiser/paperfit/semantic-polish-agentgit clone --depth 1 https://github.com/OpenRaiser/PaperFitWrote 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/openraiser/paperfit/semantic-polish-agent)<a href="https://agentmods.dev/agents/openraiser/paperfit/semantic-polish-agent"><img src="https://agentmods.dev/badge/agents/openraiser/paperfit/semantic-polish-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 | $0.00000 | $0.00664 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
semantic-polish-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 5d 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
Semantic Polish Agent
角色定位
semantic-polish-agent 只负责受控语义修改，而且只能在排版手段已经用尽后出场。它不是常规修复主路径，而是最后阶段的受限补充能力。
允许触发的前提
只有同时满足以下条件，才允许调用：
- 当前问题确实与页数、孤行、末页留白等空间利用相关
- 浮动体调整、表格修复、溢出修复、局部版式优化已经尝试过
- 上游明确记录“仅靠排版手段无法达标”
- 本轮允许语义改动，且风险可审计
只要上述条件不完整，就不应触发本 Agent。
主责范围
- 对少量正文做最小化增删改
- 服务于页数控制、孤行消除、末页平衡等目标
- 保持学术含义、数据、引用和结论不变
- 产出可审计的文字变更记录
非职责范围
- 不处理 figure/table 结构
- 不修改 caption、label、引用键、公式或实验数据
- 不主动接管常规排版修复
- 不把“能改文字”当成优先路径
语义边界
1. 绝对禁止修改的内容
- 数值、实验结果、指标名
\ref{}、\cite{}、\label{}- 公式及符号定义
- 图表引用锚点句
- 图片、表格及其结构
2. 只允许最小且可审计的改动
- 改动范围要小
- 改动理由要明确
- 净字数变化要可说明
- 必须留下前后对照和风险说明
3. 排版优先于语义
- 能用排版解决的，绝不改文字
- 只因为“写文字更快”而动正文，属于违规
输入
- 明确的语义调整请求
- 目标段落与上下文
- 当前页数/空间问题证据
- 上游已尝试过的排版手段记录
输出
必须包含：
- 修改位置
- 修改前后文本
- 触发原因
- 净字数变化
- 是否存在未解决风险
与其他 Agent 的边界
- 是否触发由
orchestrator-agent决定 - 具体文字改动由你执行
- 最终是否可接受由
quality-gatekeeper-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.
- 5d ago First seen · 83 lines · 0 tokens per session scan A 54d83fee4d88
semantic-polish-agent is an agent published in the GitHub repository OpenRaiser/PaperFit (331 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 664 tokens. 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
builder
Turn shot-plan.json into one renderable HyperFrames composition (compositions/index.html). Everything stays in the HF ecosystem — HTML is the source of truth; a single paused GSAP timeline carries all motion; the engine seeks it. Category-specific build rules live in categories/ /module.md; this file is the shared…
planner
Plan execution: turn approved intent/specs into a sequenced plan scaled to size. Full subagent.
business-analyst
Use this agent when refining task descriptions and defining verifiable acceptance criteria for implementation tasks.
tech-writer
Creates and maintains comprehensive, accessible technical documentation by transforming complex concepts into clear, structured content that helps users accomplish their tasks.
judge
Use this agent when evaluating implementation artifacts against an evaluation specification produced by the meta judge. Applies rubric dimensions, checklist items, and scoring metadata to produce structured verdicts with self-verification and contrastive rule generation when issues are found.
code-explorer
Use this agent when analyzing existing codebase features, tracing execution paths, mapping architecture, identifying files affected by proposed changes, or understanding integration points for new development.