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.constitution)<a href="https://agentmods.dev/commands/agentii-ai/blog-tech-kit/blogkit.constitution"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.constitution/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/agentii-ai/blog-tech-kit/blogkit.constitution"><img src="https://agentmods.dev/badge/commands/agentii-ai/blog-tech-kit/blogkit.constitution.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.00011 | $0.00552 |
| Opus 5.5 | $0.00004 | $0.00221 |
| Sonnet 5.5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
blogkit.constitution 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 1mo 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.constitution — 100% identical, 0 lines differ
What it actually says
Outline
Create or update blog-specific governance principles:
-
Load or Create constitution.md:
- Check if
.blogkit/memory/constitution.mdexists - If exists, read and present current principles
- If new, create with template structure
- Check if
-
Present 8 Core Blog Principles:
- Content-First: Technology choices made AFTER content strategy defined
- No Self-Validation: Technical reviews done by non-authors (avoid groupthink)
- Simplicity & Focus: No custom CMS before 10 published posts (avoid over-engineering)
- AI-Native Distribution: JSON-LD schema, H2/H3 hierarchy, FAQ sections for LLM discoverability
- Community Over Broadcast: Amplify community voices, feature contributors
- Transparency Over Perfection: Share edge cases and failure modes honestly
- Long-term Over Quick Wins: Design for 2-3 year compounding, not viral moments
- Measurable Outcomes: Every success criterion has tracking implementation
-
Get User Input (if creating new):
- Ask which principles are most important for their blog
- Ask for principle customizations/additions specific to their domain
- Offer preset profiles (Authority Blog, Practitioner Blog, Community Blog, Thought Leadership)
-
Document Principles in constitution.md sections:
- Blog Governance Framework: Core principles and definitions
- Content Strategy Principles: How content is selected and created
- Quality Gates: Validation checkpoints (Content-First, Simplicity & Focus, Constitution Check)
- Editorial Roles & Responsibilities: Writer, SME, Copyeditor, Marketing
- Success Metrics: How blog success is measured
- Constraints & Guidelines: What will/won't be published
- Review & Acceptance Checklist: 10-item gate for content acceptance
-
Link to Templates:
- Reference principles in spec-template, plan-template, tasks-template
- Show how principles gate decisions in each phase
-
Report Completion:
- Show constitution file path and size
- List all principles documented
- Show recommended next step:
/blogkit.specifyto create first blog content spec
NOTE: Constitution principles guide all downstream decisions. Establish early.
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.
- 1mo ago First seen · 53 lines · 11 tokens per session scan A 93492eec60d1
blogkit.constitution is a command published in the GitHub repository agentii-ai/blog-tech-kit (10 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 552 once invoked, about $0.0000 per session on Opus 5.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.
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
lians-recall
Recall current (non-stale) facts from Lians memory, optionally as-of a past date.