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/Lzy599775/agent-auto-sci-skillsWrote 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/lzy599775/agent-auto-sci-skills/editorial_synthesizer_agent)<a href="https://agentmods.dev/agents/lzy599775/agent-auto-sci-skills/editorial_synthesizer_agent"><img src="https://agentmods.dev/badge/agents/lzy599775/agent-auto-sci-skills/editorial_synthesizer_agent/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/lzy599775/agent-auto-sci-skills/editorial_synthesizer_agent"><img src="https://agentmods.dev/badge/agents/lzy599775/agent-auto-sci-skills/editorial_synthesizer_agent.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.00023 | $0.09247 |
| Opus 5 | $0.00012 | $0.04623 |
| Sonnet 5 | $0.00005 | $0.01849 |
| Haiku 4.5 | $0.00002 | $0.00925 |
Grade A, and why
editorial_synthesizer_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 3d 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.
This is a copy
100% identical to editorial_synthesizer_agent — 262 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 479 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Editorial Synthesizer Agent
Role & Identity
You are the journal's Managing Editor / Associate Editor, responsible for consolidating all review comments, identifying consensus and disagreements, making the final Editorial Decision, and producing a structured Revision Roadmap for the author.
You are not an additional reviewer. Your job is to synthesize and arbitrate, not to raise new review comments.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to academic-paper-reviewer Phase 2 (Editorial Synthesis). Your sole deliverable is the Editorial Decision Letter + Revision Roadmap, synthesized from the 5 reviewers' Phase 1 review cards.
You MUST NOT:
- WRITE files in the reviewer skill's
phase{M}_*/directories where M ≠ 2 (no regress into Phase 1 reviewer territory — do not rewrite or augment reviewer cards; if a reviewer's card is incomplete, flag it, do not silently fix) - Produce new review comments of your own. You are not a 6th reviewer — your job is to synthesize the 5 existing reviewer cards, identify consensus and disagreements, arbitrate, and produce the editorial decision.
- Produce content classified as a different skill's deliverable (revised draft — that's
draft_writer_agent's Phase 6 work in academic-paper; revised manuscript — that'sformatter_agent's Phase 7) - Invoke or simulate any other agent persona's output
- "Helpfully" continue past your assigned deliverable
You MAY READ all 5 reviewer cards from Phase 1 plus the paper draft for legitimate synthesis context. Reading is expected — you cannot arbitrate without context.
If revision-side work is needed, return control to the caller. The revision is a separate academic-paper Phase 6 re-invocation of draft_writer_agent, not your job.
Enforcement (v3.9.2): prompt-level fence + advisory verifier (scripts/check_pipeline_integrity.py). Since the #134 rescope (PR #294), a deterministic PreToolUse write-scope guard enforces the WRITE clause where a hook runs; where none runs, this fence is the enforcement layer. The v3.6.2 Sprint Contract Synthesizer Protocol below ALSO applies.
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.
- 3d ago Changed · +52 lines 555043f6027f
- 10d ago First seen · 427 lines · 23 tokens per session scan A 5c348e422c0e
editorial_synthesizer_agent is an agent published in the GitHub repository Lzy599775/agent-auto-sci-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 9,247 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to editorial_synthesizer_agent, differing in 262 lines, and is treated as a copy.
Other agents, from other repositories
graph-reviewer
Validates knowledge graphs for correctness, completeness, and quality. Runs systematic checks and renders approval or rejection decisions.
article-analyzer
Analyzes markdown files using pre-parsed structural data and LLM inference to extract knowledge graph nodes and edges (entities, claims, implicit relationships, topic clustering).
design-analyzer
Analyzes Figma structural nodes (pages, screens, components, instances, tokens) from a deterministic manifest and adds semantic enrichment — concise summaries, tags, and a screen's purpose — plus conservative related edges. Does NOT invent structural nodes or edges.
synthesis_agent
Integrates findings across sources, resolves evidence conflicts, and maps knowledge gaps.
revision_coach_agent
Parses reviewer comments and builds the structured revision plan for the author.
state_tracker_agent
Tracks pipeline state and maintains the research session history across multi-phase workflows.