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 skills/ololand-ai/ololand-plugins/document-editingnpx skills add ololand-ai/ololand-plugins --skill document-editinggit clone --depth 1 https://github.com/ololand-ai/ololand-pluginsWrote 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/skills/ololand-ai/ololand-plugins/document-editing)<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="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.00104 | $0.00812 |
| Opus 5 | $0.00052 | $0.00406 |
| Sonnet 5 | $0.00021 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
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 today.
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 — 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 atask_idimmediately. 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 callapprove_patchorcommit_versionthrough 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"beatsfix the revenue figure. - Pin the working set when you know the file: pass
file_idsto 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)
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.
- today First seen · 62 lines · 104 tokens per session scan A 9bd6d154ec3f
document-editing is a skill published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 6d ago), licensed Apache-2.0. It adds 104 tokens to every session and 812 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
docx-comment-reply
Reply to comments (批注) in Word .docx/.doc files: extract comment context, draft replies, write threaded replies back, and validate OOXML.