Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/shdsjh123-cpu/claude-code-blog-buildernpx agentmods add commands/shdsjh123-cpu/claude-code-blog-builder/blog-previewWrote 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/commands/shdsjh123-cpu/claude-code-blog-builder/blog-preview)<a href="https://agentmods.dev/commands/shdsjh123-cpu/claude-code-blog-builder/blog-preview"><img src="https://agentmods.dev/badge/commands/shdsjh123-cpu/claude-code-blog-builder/blog-preview/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/commands/shdsjh123-cpu/claude-code-blog-builder/blog-preview"><img src="https://agentmods.dev/badge/commands/shdsjh123-cpu/claude-code-blog-builder/blog-preview.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.00025 | $0.00280 |
| Opus 5 | $0.00013 | $0.00140 |
| Sonnet 5 | $0.00005 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
blog-preview 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 9d 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
"$ARGUMENTS" 폴더의 글에 대해 발행 어시스턴트를 엽니다.
-
폴더 경로 추정:
2026-04-09_상세페이지비용같은 폴더명만 줬다면output/$ARGUMENTS- 전체 경로면 그대로 사용
-
preview.js 실행:
node scripts/preview.js --folder "output/..." -
자동으로 브라우저가 열리며 다음 기능 제공:
- 제목·태그·메타설명 복사 버튼
- 본문 섹션별 "서식 포함 복사" / "텍스트만 복사" 두 모드
- 이미지 4장 개별/일괄 다운로드
- 발행 체크리스트 (10개 항목)
-
사용자에게 안내: "브라우저가 열렸습니다. 위에서부터 차례로 복사해서 스마트에디터에 붙여넣으시면 됩니다. 표는 복사가 안 되니 스마트에디터에서 직접 만드세요."
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.
- 9d ago First seen · 25 lines · 25 tokens per session scan A c8a1009a21bc
blog-preview is a command published in the GitHub repository shdsjh123-cpu/claude-code-blog-builder (22 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 280 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-30.
Other commands, from other repositories
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
can-i-use
Check browser support for web platform features against the project's browser targets.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
verify-pr
Verify a PR's frontend changes through browser automation.