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 skills add lfyxhappy/lfcode --skill document-editorgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/document-editor)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/document-editor"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/document-editor/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/skills/lfyxhappy/lfcode/document-editor"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/document-editor.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.00050 | $0.00321 |
| Opus 5.5 | $0.00020 | $0.00128 |
| Sonnet 5.5 | $0.00010 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
document-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 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.
What it actually says
Document Editor
Produce a document that preserves source intent, formatting requirements, and provenance.
Workflow
- Identify the input files, format, target output, audience, required sections, style or template, and whether edits must be tracked or reversible.
- Inspect document structure, metadata, embedded media, headings, tables, links, and existing styles with tools available in the workspace.
- Copy or version the source before editing. Keep factual source text distinct from editorial suggestions and mark unresolved placeholders.
- Apply the requested content or layout changes using the existing document workflow. Do not invent facts, citations, signatures, or approvals.
- Render the result with an available renderer or viewer and inspect representative and boundary pages. Also run structural checks for headings, links, tables, and output existence.
- Compare the result with the request and report changed sections, validation evidence, and limitations of the available renderer.
Boundaries
- Do not overwrite the only source, remove tracked changes, or alter metadata unrelated to the request.
- Do not upload documents or fetch external assets unless explicitly authorized.
- Treat OCR, layout approximation, and unsupported formats as uncertainty rather than silently claiming fidelity.
Completion check
Confirm the exact output path, format, render or structure checks, and any content that still needs human review.
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 · 28 lines · 50 tokens per session scan A ffe3fad260fe
document-editor is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 26d ago), licensed MIT. It adds 50 tokens to every session and 321 once invoked, about $0.0002 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-05.
Other skills, from other repositories
feishu-create-doc
A skill for creating Feishu cloud documents from Lark-flavoured Markdown, a Feishu-specific form of plain-text document formatting.
feishu-bitable
A skill for managing Feishu Bitable, a database-like spreadsheet for organising structured records. It supports tables, fields, views, filters, and bulk changes.
feishu-update-doc
A tool for updating Feishu cloud documents, including adding, replacing, inserting, and deleting text. Feishu is a collaboration platform with online documents and other workplace tools.
feishu-fetch-doc
A skill for retrieving the contents of Feishu cloud documents as Markdown. Markdown is plain text formatted with simple symbols for headings, links, and lists.
technical-writer
Becomes a senior technical writer who produces clear, accurate, and audience-appropriate documentation including API references, developer guides, changelogs, and onboarding materials. Use when the user needs documentation written, restructured, or improved for technical or non-technical audiences. Do NOT use when…
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.