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.
git 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.analyze)<a href="https://agentmods.dev/commands/agentii-ai/blog-tech-kit/blogkit.analyze"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.analyze.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.00659 |
| Opus 5 | $0.00006 | $0.00329 |
| Sonnet 5 | $0.00003 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
blogkit.analyze 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 8d 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.analyze — 100% identical, 0 lines differ
What it actually says
Outline
Perform comprehensive cross-artifact consistency analysis:
-
Load all artifacts: spec.md, plan.md, tasks.md (and research.md if exists)
-
Content-First Validation:
- Verify spec.md contains ZERO technology implementation details
- Verify plan.md contains all tech stack decisions
- Flag any technology mentions in spec.md
-
Requirement Traceability:
- Map each requirement (CR-001 to CR-020) from spec.md to plan.md sections
- Map each plan section to tasks.md sprint/phase
- Identify requirements with no corresponding tasks (coverage gaps)
-
Success Criteria Alignment:
- Verify all success criteria (SC-001 to SC-016) from spec.md are addressed in plan.md
- Check that tasks.md includes measurement tasks for each SC
- Identify success criteria without tracking implementation
-
Blog Type Consistency:
- Verify blog type is consistent across all three documents
- Check editorial workflow matches blog type (Authority 6-week vs. Practitioner 2-week)
- Verify content pillars mentioned in plan match spec
-
Timeline & Sprint Consistency:
- Verify Sprint 0 duration matches plan.md platform setup timeline
- Check sprint count (should be 5 content sprints per plan)
- Validate sprint dependencies align between plan and tasks
-
Team & Role Consistency:
- Verify roles defined in plan.md (Writer, SME, Copyeditor, Marketing) are referenced in tasks
- Check task assignments match role responsibilities
-
Constitution Principle Enforcement:
- Verify all 8 Blog Principles are addressed in plan.md Constitution Check section
- Check that tasks.md includes quality gate checkpoints
- Ensure no Self-Validation principle enforced (SME review in tasks)
-
Dependency Analysis:
- Map task dependencies in tasks.md
- Verify Sprint 0 is prerequisite for all content sprints
- Check that measurement tasks reference analytics from plan
-
Generate Analysis Report:
- Create markdown report at
FEATURE_DIR/analysis-report.md - List all consistency checks passed/failed
- For failures, show specific lines/sections that conflict
- Provide remediation recommendations
- Calculate "Consistency Score" (% of checks passed)
- Create markdown report at
-
Report Results:
- Display consistency score
- List any gaps found (requirements not addressed in tasks)
- List any inconsistencies (conflicting information)
- Show overall assessment (PASS/FAIL/REVIEW_RECOMMENDED)
- If issues found, ask user: "Review and fix issues, then re-run analyze?"
NOTE: Cross-artifact analysis catches planning gaps before execution starts.
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.
- 8d ago First seen · 74 lines · 13 tokens per session scan A 97d0d9e5d8ca
blogkit.analyze 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 659 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
A command that runs a complete Excalibur BLOG article process through an orchestrator and supporting agents.
excalibur-blog-setup
An interactive setup command for an Excalibur BLOG project.
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
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.