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 singula-ai/alego --skill office-rendergit clone --depth 1 https://github.com/singula-ai/alegoWrote 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/singula-ai/alego/office-render)<a href="https://agentmods.dev/skills/singula-ai/alego/office-render"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/office-render/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/singula-ai/alego/office-render"><img src="https://agentmods.dev/badge/skills/singula-ai/alego/office-render.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.00016 | $0.00976 |
| Opus 5.5 | $0.00006 | $0.00390 |
| Sonnet 5.5 | $0.00003 | $0.00195 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
office-render 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 2d 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
91% identical to office-render — 2 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document images and visual inspection
Use the installed LibreOffice Kit CLI through the shell with the absolute Node and CLI paths supplied below. In Bash, invoke "<node>" "<cli>"; in PowerShell, invoke & "<node>" "<cli>". Prefer bundled LibreOffice unless the user requests another installation. If the Office sidecar is missing, follow sidecar setup: ask whether the user wants to download it and install only after they agree. Do not invoke system soffice, use npx, install a replacement renderer, or build an alternative rendering pipeline to work around a failed render with an installed sidecar.
Before generating images only for inspection, establish that the current model accepts images. Otherwise finish the applicable content and structure checks and report the requested visual check as unavailable. Do not generate unreadable previews, retry image reads, or choose a second model. Requested image exports can still be delivered.
Render the saved deliverable
Keep the saved deliverable in the task workspace. For requested image exports, use the requested output directory and retain the images. For inspection-only previews, create a private, uniquely named temporary parent inside that workspace and pass a child path that does not yet exist as --output-dir; the CLI creates that child. On POSIX, use preview_root=$(mktemp -d "./.alego-office.XXXXXXXX") (owner-only permissions) and --output-dir "$preview_root/render". On PowerShell, create a parent named .alego-office- plus [guid]::NewGuid().ToString('N') under the task workspace and pass an uncreated render child; it inherits the workspace ACL. Quote each input and output path. Retain the parent until image inspection finishes, then remove only that parent, including after a failed render. Never use a fixed directory name or remove the workspace itself. Report inspection results in text; the reply must not link or embed removed previews.
"<node>" "<cli>" render --input <final-file> --output-dir <new-directory> --pages "1,3,4"
"<node>" "<cli>" render --input <final-workbook.xlsx> --output-dir <new-directory> --sheet <exact-name> --range <A1-range>
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.
- 2d ago First seen · 32 lines · 16 tokens per session scan A e8ec835a0ed3
office-render is a skill published in the GitHub repository singula-ai/alego (109 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 976 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to office-render, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
office-docx
A tool for creating and reading editable Microsoft Word documents in the .docx format. It supports common document parts such as headings, paragraphs, tables, code blocks, lists, and centred titles.
impact-report-writer
Nonprofit/NGO impact report generation with data visualization suggestions, outcome metrics, narrative structure, and program data presentation. Use when writing impact reports, annual reports, or program evaluation summaries.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
codebase-documenter
Write codebase documentation: READMEs, architecture docs, getting-started guides, API docs, and code comments. Use when documenting code or making a project easier for new developers.
agent-documentation-writer
Specialist subagent: Generates comprehensive documentation including READMEs, API docs, architecture docs, and inline comments. Use when documenting code, creating guides, or explaining systems.
harness
Use when governing a workspace's control plane, code or not — the 01-TOOLS/ tooling layer, the 02-DOCS/ chaos→knowledge wiki, the root Knowledge map. Audits it, migrates legacy XX- folders, scaffolds provider tooling, sweeps the inbox, eats a file the person hands over ("cómete este fichero", "guárdalo en la…