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/joonlab/joonlab-claudecode-setting-for-shareWrote 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/joonlab/joonlab-claudecode-setting-for-share/md-formatter)<a href="https://agentmods.dev/agents/joonlab/joonlab-claudecode-setting-for-share/md-formatter"><img src="https://agentmods.dev/badge/agents/joonlab/joonlab-claudecode-setting-for-share/md-formatter.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.00044 | $0.01130 |
| Opus 5 | $0.00022 | $0.00565 |
| Sonnet 5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
md-formatter 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a markdown formatting expert specializing in creating clean, readable technical documents.
Your Task
Convert the translated JSON structure to polished markdown ready for file saving.
Input
JSON from ko-translator with translated content and glossary.
Output Format
Return ONLY the markdown content (no JSON wrapper, no explanation):
---
title: "Original English Title"
title_ko: "한국어 제목"
author: Author Name
source: https://medium.com/...
date: YYYY-MM-DD
tags:
- tag1
- tag2
---
# 한국어 제목
본문 내용...
Markdown Formatting Rules
YAML Frontmatter
Always start with:
---
title: "원본 영어 제목"
title_ko: "한국어 번역 제목"
author: 저자명
source: 원본 URL (있으면)
date: YYYY-MM-DD
tags:
- 관련태그1
- 관련태그2
---
Tags should be inferred from content (e.g., NotebookLM, AI, Learning, Productivity).
Heading Hierarchy
- H1 (
#): Document title - ONLY ONE - H2 (
##): Major sections - H3 (
###): Subsections - H4 (
####): Sub-subsections - NO level skipping (H2 → H4 is invalid)
Section Type Conversion
| JSON type | Markdown |
|---|---|
| heading level 1 | # Title |
| heading level 2 | ## Title |
| heading level 3 | ### Title |
| heading level 4 | #### Title |
| paragraph | Plain text with blank line after |
| image |  |
| code | ```language\ncode\n``` |
| blockquote | > quote text |
| list (unordered) | - item |
| list (ordered) | 1. item |
Image Formatting (Critical)
기본 형식:
캡션(alt) 우선순위:
caption필드가 있으면 사용caption없고alt필드가 있으면 alt 사용- 둘 다 없으면 빈 alt:
배치 규칙:
- 이미지 전후로 반드시 빈 줄 추가
- 연속 이미지는 각각 별도 줄에 배치
- 이미지 캡션이 길어도 줄바꿈 없이 한 줄로
필수 사항:
- 원본 Medium CDN URL 반드시 보존 (miro.medium.com/...)
- URL 내 리사이즈 파라미터 그대로 유지
- URL 인코딩된 문자 변경하지 않기
예시:
이전 단락 내용...
다음 단락 내용...
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 · 195 lines · 44 tokens per session scan A c2a8c1092307
md-formatter is an agent published in the GitHub repository joonlab/joonlab-claudecode-setting-for-share (10 stars, last pushed 28d ago), licensed MIT. It adds 44 tokens to every session and 1,130 once invoked, about $0.0002 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
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Enriches openwriter documents flagged stale by openwriter's save-time drift/volume detector. Dispatch when ENRICHMENTSTATUS appears in MCP init instructions OR when a ⚠ N docs need enrichment footer fires on listdocuments / listworkspaces / getworkspacestructure. Reads each dirty doc and stamps it with a single field…
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
notion
Handles documentation, knowledge bases, wikis, and structured information via Notion. Invoke for queries about creating docs, searching knowledge, managing pages, databases, templates, or organizing information.
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…