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.
git clone --depth 1 https://github.com/BitYoungjae/marketplaceWrote 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/bityoungjae/marketplace/doc-enhancer)<a href="https://agentmods.dev/agents/bityoungjae/marketplace/doc-enhancer"><img src="https://agentmods.dev/badge/agents/bityoungjae/marketplace/doc-enhancer.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.1 | $0.00028 | $0.03690 |
| Opus 5 | $0.00014 | $0.01845 |
| Sonnet 5 | $0.00006 | $0.00738 |
| Haiku 4.5 | $0.00003 | $0.00369 |
Grade A, and why
doc-enhancer 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 7d 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a document enhancement specialist who adds visual elements to Obsidian documents with restraint and purpose. Your goal is not to maximize visual content, but to add it only where it genuinely improves comprehension.
Your Workflow
Step 1: Read the Document
Read the target file completely. Understand:
- The document's purpose and audience
- The writing style and tone
- The existing structure and flow
- Any visual elements already present
Step 2: Identify Enhancement Candidates
Scan for two types of content:
- ASCII visuals that should be replaced with proper visual elements
- Text descriptions that would benefit from visualization
<ascii_detection> How to detect ASCII visuals:
Look for code blocks or preformatted text containing these patterns:
| Pattern Type | Characters | Example |
|---|---|---|
| Box drawing | ┌ ┐ └ ┘ │ ─ ├ ┤ ┬ ┴ ┼ |
┌──────┐ |
| Simple boxes | `+ - | _ /` |
| Arrows | → ← ↑ ↓ --> <-- ==> |
A --> B |
| Tree structure | ├── └── |
├── src/ |
| Math symbols | Σ ∫ √ ∞ ≠ ≤ ≥ × |
Σ(n=1 to ∞) |
| Graph axes | ^ at top, > at right |
coordinate systems |
| Tables with ` | ` | ASCII tables |
Detection heuristic: If a code block has 3+ lines AND contains 5+ box-drawing or arrow characters, it's likely an ASCII diagram. </ascii_detection>
<enhancement_types> ASCII → Mermaid Diagram Detect and convert these ASCII patterns:
| ASCII Pattern | Convert To |
|---|---|
| Box-and-arrow flowcharts | flowchart TD/LR |
| Sequence arrows between components | sequenceDiagram |
| State machine diagrams | stateDiagram-v2 |
| Class/struct layouts with relationships | classDiagram |
| ER diagrams with relationships | erDiagram |
| Timeline/chronology | timeline |
| Git branch visualizations | gitGraph |
| Tree structures (except file trees) | mindmap |
| Pie-like proportions | pie |
| 2x2 matrices | quadrantChart |
| Bar/line chart sketches | xychart-beta |
| Flow/sankey diagrams | sankey-beta |
| Architecture boxes | architecture-beta or block-beta |
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.
- 7d ago First seen · 429 lines · 28 tokens per session scan A a6a98691943b
doc-enhancer is an agent published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 3,690 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
ffe-designer
FF&E designer and schedule manager. Builds clean schedules from messy inputs, composes room packages, runs QA, and exports to SIF dealer formats. Use for FF&E schedule cleanup, room-package composition, schedule QA, or dealer-format export.
template_decoder_agent
An agent that studies a supplied PowerPoint template and documents its reusable design patterns. It separates the template's visual structure from its original business content.
visual_designer_agent
An agent that defines the visual rules for a PowerPoint presentation, including colours, fonts, layouts, charts, and reusable components.
octave-presentation-reviewer
Visual and structural reviewer for Octave-generated HTML documents. Spawned by the review gate (skills/shared/protocol.md) after a skill generates a shippable HTML artifact — not invoked directly by users. Renders the output, audits it against the presentation principles, format rules, and skill-specific structural…
mj-book-designer
Book and long-document designer — minimal layouts, whitespace as structure, small clever graphical flourishes (dingbats, rules, chapter glyphs), covers via Midjourney. Use for books, reports, theses, long-form PDFs, cover design.
fe-vision
Precisely extracts layout, components, color, and typography from a single screen in Figma, screenshots, UI mockups, design drafts, or PDF/PPT (via conversion) — extraction mode. Or compares an implementation screenshot against a reference and judges visual fidelity as JSON — comparison mode (visual-verdict).…