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.specifygit 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.specify)<a href="https://agentmods.dev/commands/agentii-ai/blog-tech-kit/blogkit.specify"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.specify.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.00015 | $0.04064 |
| Opus 5 | $0.00008 | $0.02032 |
| Sonnet 5 | $0.00003 | $0.00813 |
| Haiku 4.5 | $0.00002 | $0.00406 |
Grade A, and why
blogkit.specify 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.specify — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 329 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
The text the user typed after /blogkit.specify in the triggering message is the blog content strategy description. Assume you always have it available in this conversation even if $ARGUMENTS appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that blog strategy description, do this:
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the blog strategy description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the blog strategy
- Use noun-focused format when possible (e.g., "authority-blog-ml", "practitioner-tutorials", "community-spotlight")
- Preserve blog type indicators (authority, practitioner, community, thought-leadership)
- Keep it concise but descriptive enough to understand the blog type at a glance
- Examples:
- "I want to create an authority blog for ML engineers" → "authority-blog-ml"
- "Build practitioner tutorials for LangChain developers" → "practitioner-langchain-tutorials"
- "Launch community spotlight blog" → "community-spotlight-blog"
- "Create thought leadership content for AI founders" → "thought-leadership-ai-founders"
-
Check for existing branches before creating new one:
a. First, fetch all remote branches to ensure we have the latest information:
git fetch --all --pruneb. Find the highest feature number across all sources for the short-name:
- Remote branches:
git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$' - Local branches:
git branch | grep -E '^[* ]*[0-9]+-<short-name>$' - Specs directories: Check for directories matching
specs/[0-9]+-<short-name>
c. Determine the next available number:
- Extract all numbers from all three sources
- Find the highest number N
- Use N+1 for the new branch number
- Remote branches:
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 · 329 lines · 15 tokens per session scan A e8cb8826c33e
blogkit.specify is a command published in the GitHub repository agentii-ai/blog-tech-kit (10 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 4,064 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 — интерактивная инициализация и настройка проекта.
init
Initialize configurations for Supabase local development.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
handoff
Export a Waybill Bundle by default, or import one when requested.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.