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 commands/agentii-ai/blog-tech-kit/blogkit.clarifygit clone --depth 1 https://github.com/agentii-ai/blog-tech-kitWrote 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/agentii-ai/blog-tech-kit/blogkit.clarify)<a href="https://agentmods.dev/commands/agentii-ai/blog-tech-kit/blogkit.clarify"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.clarify.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.00013 | $0.01382 |
| Opus 5 | $0.00006 | $0.00691 |
| Sonnet 5 | $0.00003 | $0.00276 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
blogkit.clarify 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- blogkit.clarify — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
Given the blog content strategy specification (spec.md), identify underspecified areas and ask clarification questions:
-
Load and Analyze spec.md:
- Read spec.md from current feature directory
- Scan for [NEEDS CLARIFICATION] markers and vague sections
- Identify ambiguous areas in: Blog Type, Target Audience, Content Pillars, Success Criteria
-
Prioritize Clarifications:
- Priority 1 (Scope Impact): Blog type, target audience definition, content pillar focus
- Priority 2 (Quality Impact): Publishing cadence, content length, quality standards
- Priority 3 (Distribution Impact): Distribution channels, social strategy, engagement goals
- LIMIT: Ask MAXIMUM 3 clarification questions across all priorities
-
Generate Clarification Questions:
- For each clarification need, create a focused question with 3-4 suggested answers
- Include context from spec.md showing why clarification is needed
- Provide implications of each answer option
- Format as markdown table for clarity
-
Present Questions to User:
- Number questions Q1, Q2, Q3 (max 3)
- Present all questions together before waiting for responses
- Use clear markdown formatting with tables for options
- Include context quotes from spec.md
-
Wait for Responses:
- Ask user to respond with format: "Q1: [Option], Q2: [Custom answer], Q3: [Option]"
- Accept option letters (A, B, C, Custom) or full custom text
- Wait for complete set of responses before proceeding
-
Update spec.md:
- Replace [NEEDS CLARIFICATION] markers with user's answers
- Add "Clarifications" section documenting Q&A pairs
- Maintain all existing spec content unchanged
- Preserve formatting and structure
-
Validate Updates:
- Confirm spec.md no longer contains [NEEDS CLARIFICATION] markers (or max 1-2 remaining)
- Verify clarifications are consistent with rest of spec
- Check for any new ambiguities that clarifications introduced
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.
- 6d ago First seen · 148 lines · 13 tokens per session scan A 42f34eb75bf0
blogkit.clarify is a command published in the GitHub repository agentii-ai/blog-tech-kit (10 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 1,382 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 commands, from other repositories
excalibur-blog-run
Excalibur BLOG — полный прогон статьи через оркестратор и субагентов.
excalibur-blog-setup
Excalibur BLOG — интерактивная инициализация и настройка проекта.
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
init
Initialize configurations for Supabase local development.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
release
Walk the llmwiki release process step by step.