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-qualityWrote 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-quality)<a href="https://agentmods.dev/commands/shdsjh123-cpu/claude-code-blog-builder/blog-quality"><img src="https://agentmods.dev/badge/commands/shdsjh123-cpu/claude-code-blog-builder/blog-quality/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-quality"><img src="https://agentmods.dev/badge/commands/shdsjh123-cpu/claude-code-blog-builder/blog-quality.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.00020 | $0.00260 |
| Opus 5 | $0.00010 | $0.00130 |
| Sonnet 5 | $0.00004 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
blog-quality 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-08_상세페이지AI같은 폴더명만 줬다면output/$ARGUMENTS/post.md - 전체 경로면 그대로 사용
- 사용자가
-
품질검사:
node scripts/quality-check.js --file "output/.../post.md" --keyword "<폴더명에서 추출>" -
유사도 검사:
node scripts/duplicate-check.js --file "output/.../post.md" -
결과를 표 형식으로 사용자에게 보고:
- 전 항목 PASS/WARN 상태
- 유사도 상위 3건
- 경고가 있으면 어느 부분을 어떻게 수정할지 구체 제안 (수정은 하지 않음, 제안만)
사용자가 "고쳐줘" 라고 하면 그때 Edit으로 수정 후 재검사.
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 · 28 lines · 20 tokens per session scan A ad2f709cec97
blog-quality is a command published in the GitHub repository shdsjh123-cpu/claude-code-blog-builder (22 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 260 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.