What is document-editing?

A document-editing workflow that proposes changes to deal documents as reviewable patches. A human must approve and commit each accepted change, creating a new document version with its evidence and history.

Correcting figures, names, or wording across deal documents and reviewing proposed before-and-after changes.

It allows corrections while keeping human control, approval records, document history, and the evidence behind every edit.

document-editing — Skill for Claude Code by ololand-ai/ololand-plugins

Install

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.

Any agent

npx skills add ololand-ai/ololand-plugins --skill document-editing

Clone the repo

git clone --depth 1 https://github.com/ololand-ai/ololand-plugins

Made for: Claude Code.

Or install ololand-dd, the plugin that ships this one along with the rest of its 22 skills, 54 commands, 3 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/document-editing/github.svg)](https://agentmods.dev/skills/ololand-ai/ololand-plugins/document-editing)

Your own site

<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/document-editing"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/document-editing/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ololand-ai/ololand-plugins/document-editing"><img src="https://agentmods.dev/badge/skills/ololand-ai/ololand-plugins/document-editing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 812 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00104	$0.00812
Opus 5.5	$0.00042	$0.00325
Sonnet 5.5	$0.00021	$0.00162
Haiku 4.5	$0.00010	$0.00081

Measured 1mo ago against content hash 9bd6d154ec3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

document-editing 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.

plugins/ololand-dd/skills/document-editing/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Document Editing (human-approved patches)

OloLand can edit deal documents agentically — but it never commits anything itself. An editing agent mounts the relevant documents, makes the edits, and each accepted edit becomes a pending_approval patch that passes four deterministic verifiers. A human reviews, approves (or rejects) and commits patches into a new document version. Full provenance: proposer, rationale, evidence quote, verifier verdicts, approval note, version lineage.

The flow (launch → poll → read → approve)

Launch: edit_deal_documents(deal_id, instruction, file_ids?) — returns a task_id immediately. Costs 10 credits. Sessions take seconds to a couple of minutes.
Poll: check_task_status(task_id) until completed.
Read: list_patches(deal_id, status="pending_approval") — patches are DB-backed and stay readable after the task id expires. Each patch carries op, before/after text, evidence, and verifier verdicts.
Approve & commit (HUMAN step): in the web app under Deal → Document Edits (/deals/<deal_id>/patches). The MCP rail is fail-closed for human approvals: never call approve_patch or commit_version through MCP. Never auto-approve on the user's behalf — surface the pending patches and let the user decide in the app.

Writing instructions that land deterministically

Quote the exact text to change: replace "FY2024 revenue of $12.4M" with "FY2024 revenue of $12.6M" beats fix the revenue figure.
Pin the working set when you know the file: pass file_ids to skip retrieval-based candidate discovery — faster and unambiguous.
One logical change per instruction. The editing agent keeps each edit inside one paragraph; cross-paragraph rewrites are rejected.
Repeated text (OCR'd forms, boilerplate): the agent uses replace-all semantics — each occurrence becomes its own patch; the reviewer can approve them individually.

What gets rejected (and why that's the product)

Read the full file on GitHub · 62 lines

Changes

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 · 62 lines · 104 tokens per session scan A 9bd6d154ec3f

Subscribe to this mod's changes

document-editing is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 3d ago), licensed Apache-2.0. It adds 104 tokens to every session and 812 once invoked, about $0.0004 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.

Documents Legal and compliance

html-ppt-zhangzara-stencil-tablet

A workplace-safety compliance review for a manufacturing regulator — findings, the evidence chain, and the corrective mandate. Built as a decision-grade policy briefing deck for regulator, plant leadership.

nexu-io/open-design · 49 tokens

treatment-plans

Formats and structurally validates local treatment-plan documentation after clinical decisions have already been supplied and verified by authorized licensed professionals. Use for source traceability, clinician-authored intervention records, goals and checkpoints, shared-decision records, reconciliation handoffs, and…

K-Dense-AI/scientific-agent-skills · 62 tokens

legal-hold

Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.

anthropics/claude-for-legal · 68 tokens

document-editing