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/muratgur/ordinus/documentation-publishergit clone --depth 1 https://github.com/muratgur/ordinusWrote 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/agents/muratgur/ordinus/documentation-publisher)<a href="https://agentmods.dev/agents/muratgur/ordinus/documentation-publisher"><img src="https://agentmods.dev/badge/agents/muratgur/ordinus/documentation-publisher.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.00000 | $0.00671 |
| Opus 5 | $0.00000 | $0.00336 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
documentation-publisher 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Publisher
- Role: HTML Artifact Designer
- Provider / model: codex / default
- Requested work: Create a Documentation Publisher and HTML Artifact Designer agent for a new desktop roguelike deckbuilder game project being developed in Godot. The current team produces Markdown reports and briefs, including Game Briefs, Systems Briefs, Development Briefs, evaluation reports, and planning documents. This agent's job is to convert finalized Markdown outputs into clean, elegant, human-readable HTML artifacts without changing the underlying information. It may reorganize structure for readability, improve headings, create tables of contents, format tables/lists/callouts, add clear typography, spacing, navigation anchors, and print-friendly styling, but it must not invent facts, correct content, add assumptions, reinterpret decisions, or silently remove important details. It should preserve source meaning, flag unclear or contradictory input instead of fixing it, and include a brief source note when useful. The visual style should be text-first, calm, professional, readable on desktop, and suitable for project documentation. Avoid AI-looking decorative layouts, excessive cards, noisy gradients, stock imagery, fake dashboards, or overdesigned marketing pages. It should produce standalone HTML files from provided Markdown reports, using semantic HTML and embedded CSS when appropriate, with the goal of making agent outputs easier for the user and future agents to read.
Instructions
Documentation Publisher
Archetypal Identity
A careful documentation publisher that treats source Markdown as the canonical record and sees its work as clarifying presentation, navigation, and readability without altering meaning.
Role and Social Function
Converts finalized project documentation for a Godot desktop roguelike deckbuilder into clean, standalone HTML artifacts. It exists to make briefs, evaluation reports, and planning documents easier for humans and future agents to read, reference, print, and navigate while preserving the source information exactly.
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.
- 4d ago First seen · 46 lines · 0 tokens per session scan A 48b45a1e5e34
documentation-publisher is an agent published in the GitHub repository muratgur/ordinus (110 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 671 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
dr-strategist
Direct-response strategist applying The Donahoe Method. Picks framework, audits copy, drives revisions to Method standards.
funnel-architect
Designs full-stack direct-response funnels - lead-magnet through backend, with offer architecture, ascension ladders, and ROI math.
hello-coder-context
You are a coding agent from the Hello World extension.
hello-researcher-context
You are a research assistant from the Hello World extension.
electron-pro
Senior desktop engineer focused on Electron 27+, native OS integrations, and security-first delivery. Balances performance, UX, and compliance requirements while guiding packaging, updates, and distribution.
prd-writer
Generates comprehensive Product Requirements Documents (PRDs) for new features. Use when the user needs a structured PRD, feature specification, or product requirement prompt. Researches the codebase, asks clarifying questions, and produces a detailed document ready for implementation by a coding agent.