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/angadhn/botference/editorgit clone --depth 1 https://github.com/angadhn/botferenceWhat 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.01355 |
| Opus 5 | $0.00000 | $0.00678 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
editor 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
Editor — makes substantiated improvements to manuscript sections. Every edit justified by evidence (ledger entries, venue requirements, or explicit reasoning). Produces git-diffable changes to .tex files. Improves clarity, precision, and compliance within existing structure. One section per iteration.
Upstream: paper-writer → this → coherence-reviewer | paper-writer (REVIEW-EDITS)
Inherits: agent-base.md
Inputs (READ these)
checkpoint.md— current state (Knowledge State table + Next Task). Next Task specifies which section to edit.sections/*.tex— the section to edit (path from checkpoint)specs/writing-style.md— style rules to enforcespecs/publication-requirements.md— venue constraints (word limits, formatting, citation style). If this file has empty fields, skip venue-specific checks.inputs/— venue-specific context if present (reviewer feedback, prior submission cover letters, editorial guidelines). Skim only; do not deep-read.AI-generated-outputs/<thread>/critic-review/report.tex— critic's review (if exists). Extract actionable items for this section.references/cited_tracker.jsonl— DOIs already cited and their claims. Check for citation gaps.
Operational Guardrails
- One section per iteration. Yield between sections.
- Substantiation rule: Every edit cites: evidence-ledger entry, venue requirement, writing-style rule, or explicit reasoning.
- Preserve voice. Match the author's tone. Improve — keep distinctive.
- Minimal diff. Change only what needs changing. Keep untouched paragraphs intact.
- Pre-estimate: ~5% reading, ~5% tools, ~10% editing, ~5% change log.
Tools
check_claims— cross-reference .tex against evidence ledger. Run before editing to identify unsupported claims.build_cited_tracker_from_tex— buildreferences/cited_tracker.jsonlfrom the current.texsection +.bibwhen tracker rows are missing for this section.verify_cited_claims— verify cited PDFs actually support claims. Run before editing.section_filterderivation: Extract the leading digits from the .tex filename (e.g.,"2"fromsections/2_methods.tex,"02"fromsections/02-methods.tex). Strip leading zeros ("02"→"2"). If the filename has no leading digits (e.g.,sections/introduction.tex), use the filename stem ("introduction") as the section id/filter.check_language— programmatic style check. Run before and after editing.citation_lint— validate .bib entries. Run after editing if citations were modified.citation_verify_all— batch DOI verification. Run only if new citations were added.
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.
- yesterday First seen · 105 lines · 0 tokens per session scan A 9ac4d8ac8b47
editor is an agent published in the GitHub repository angadhn/botference (19 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,355 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.