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.tasksgit 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.tasks)<a href="https://agentmods.dev/commands/agentii-ai/blog-tech-kit/blogkit.tasks"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.tasks.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.00009 | $0.02866 |
| Opus 5 | $0.00005 | $0.01433 |
| Sonnet 5 | $0.00002 | $0.00573 |
| Haiku 4.5 | $0.00001 | $0.00287 |
Grade A, and why
blogkit.tasks 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 5d 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.tasks — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 307 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 editorial plan (plan.md) and any technical context from the user, generate a comprehensive task breakdown for content production:
-
Load Required Plan File:
- Read
plan.mdfrom the current feature directory - Extract: Editorial Workflow, Content Calendar, First 5 Posts structure, Technical Stack
- Read
-
Validate Plan Completeness:
- Confirm plan.md contains all required sections
- Verify Constitution Check passed (all 8 Blog Principles validated)
- Verify no [NEEDS CLARIFICATION] markers remain
- If validation fails: STOP and ask user to complete plan using
/blogkit.plan
-
Parse Blog Structure from Plan:
- Extract: Blog Type, Target Audience, Content Pillars, Publishing Cadence
- Identify: First 5 post titles (or post types if titles not yet defined)
- Extract: Expected timeline for each sprint (from Editorial Workflow section)
- Identify: Team structure (Writer, SME, Copyeditor, Marketing roles)
-
Load Sprint 0 Template:
- Use
.blogkit/templates/tasks-template.mdSprint 0: Platform Setup - Customize timing based on plan.md (1-2 weeks for platform setup)
- Customize platform choices from Technical Stack section
- Customize team roles from Editorial Workflow section
- Use
-
Generate Content Sprint Tasks (Sprints 1-5):
For each of the first 5 posts defined in plan.md:
a. Determine Post Type and Timeline:
- Post 1 (Foundation): Authority-establishing post on core concept
- Timeline: 6-week cycle (Authority blogs) or 2-week cycle (Practitioner blogs)
- Post 2 (Deep Dive): Advanced exploration building on Post 1
- Timeline: Same as Post 1
- Post 3 (Anti-Pattern): Credibility through failure documentation
- Timeline: Same as Post 1
- Post 4 (Ecosystem): Positioning in broader context
- Timeline: Same as Post 1
- Post 5 (Benchmark/Data): Original research establishing authority
- Timeline: Same as Post 1 + 1 week for research
- Post 1 (Foundation): Authority-establishing post on core concept
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.
- 5d ago First seen · 307 lines · 9 tokens per session scan A 3863ca4c7b11
blogkit.tasks is a command published in the GitHub repository agentii-ai/blog-tech-kit (10 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 2,866 once invoked, about $0.0000 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.