Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/eddiebelaval/squire/publish-essay)<a href="https://agentmods.dev/commands/eddiebelaval/squire/publish-essay"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/publish-essay.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.00000 | $0.00811 |
| Opus 5 | $0.00000 | $0.00405 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
publish-essay 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/publish-essay - Publish Essay to id8labs.app
Create MDX file, commit to id8labs-hub repo, and trigger Vercel deploy.
Usage
/publish-essay "<title>" --content <mdx-content>
/publish-essay --from-file <path> # Publish from existing MDX file
/publish-essay --slug custom-slug # Override auto-generated slug
Process
-
Validate Content
- Ensure frontmatter is complete (title, date, category required)
- Verify content is in proper MDX format
- Check that category is one of: essay, research, release
- Generate slug from title if not provided (kebab-case)
-
Create MDX File
- Location:
/Users/eddiebelaval/Development/id8labs-hub/core/content/essays/ - Filename:
{slug}.mdx - Add/verify all required frontmatter fields
- Location:
-
Git Operations
cd /Users/eddiebelaval/Development/id8labs-hub git checkout main git pull origin main git add core/content/essays/{slug}.mdx git commit -m "content: add essay - {title}" git push origin main -
Trigger Deploy
- Push to main triggers Vercel auto-deploy
- Monitor deploy status with
vercel inspect - Wait for production deploy completion
-
Return Essay URL
- Format:
https://id8labs.app/essays/{slug} - Verify URL is accessible (may take 1-2 minutes)
- Format:
MDX Frontmatter Reference
---
title: "Required - Essay title"
subtitle: "Optional - Supporting tagline"
date: "YYYY-MM-DD" # Required
author: "Eddie Belaval" # Optional, defaults to Eddie
category: "essay|research|release" # Required
tags: ["tag1", "tag2"] # Optional
featured: true|false # Optional
heroImage: "/path/to/image.webp" # Optional
---
Content Guidelines
- Use standard Markdown syntax
- Code blocks with language identifiers
- No JSX components (pure Markdown)
- Images should be in /public/ or external URLs
- Estimated read time calculated automatically (~200 wpm)
Example
/publish-essay "The 70% Problem" --content "---
title: \"The 70% Problem\"
subtitle: \"Why AI tools get us most of the way, then leave us stranded\"
date: \"2025-12-30\"
author: \"Eddie Belaval\"
category: \"research\"
tags: [\"research\", \"ai\", \"productivity\"]
---
I've been tracking something for the past six months...
[Full essay content]
"
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.
- 4d ago First seen · 115 lines · 0 tokens per session scan A ebb52fef2dbf
publish-essay is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 811 tokens. 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-09-03.
Other commands, from other repositories
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
copush
Pull, version-bump, commit all changes, and push to origin.
commit-push-pr
Commit, push, and open a PR.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
commit-push-pr
Commit, push, and open a PR (includes changeset creation).
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.