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/arome3/code-to-content/newslettergit clone --depth 1 https://github.com/arome3/code-to-contentWrote 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/arome3/code-to-content/newsletter)<a href="https://agentmods.dev/commands/arome3/code-to-content/newsletter"><img src="https://agentmods.dev/badge/commands/arome3/code-to-content/newsletter.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 | $0.00008 | $0.00583 |
| Opus 5 | $0.00004 | $0.00292 |
| Sonnet 5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
newsletter 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Newsletter Issue
Create a newsletter issue featuring updates from the provided project.
Differentiation Discovery (offer; never blocking): Before generating, offer to make this unmistakably theirs — ask for the WHY (the thesis/stakes), one defensible opinion, a road not taken, or a rough draft to polish ("write it ugly; I'll keep your voice"). Rank raw material (Slack threads, support tickets, a voice-memo transcript) above clean specs. If declined, proceed on code alone and flag
Distinctiveness: AT RISK. At delivery, run the swap-the-name test + AI-tells blocklist fromreferences/differentiation.md.
Process
-
Analyze Recent Changes Analyze the codebase Claude-natively (read dependency files, detect architecture, grep story hooks like TODO/FIXME, mine
git log) — seereferences/analysis-prompts.md. No scripts required. Also examine recent git history for story-worthy commits. -
Load Skill Context Read these files:
skills/code-to-content/SKILL.mdskills/code-to-content/references/differentiation.md(WHY / opinion / roads-not-taken)skills/code-to-content/references/newsletters.mdskills/code-to-content/assets/templates/newsletter.md
-
Identify Newsletter Format Ask the user which format fits their update:
- Build Log: Active development (shipped, learned, next)
- Deep Dive: After completing significant feature
- Lesson Learned: After resolving a challenge
- Milestone Update: Reached a significant goal
-
Extract Content Elements
- Featured item (main update or insight)
- Quick hits (3-5 smaller updates)
- Code snippet or visual if applicable
- Personal reflection or lesson
- What's next / roadmap tease
-
Generate Newsletter Include:
- Subject line (under 50 chars, creates curiosity)
- Preview text (120-160 chars)
- Personal opening hook (conversational)
- Featured section with unique commentary
- Quick hits with your perspective (not just changelog)
- Engaging closing with CTA
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 · 59 lines · 8 tokens per session scan A 43a4a9b2591b
newsletter is a command published in the GitHub repository arome3/code-to-content (6 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 583 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
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
archive
Archive merged feature specs into project memory with provenance, sweep discovery, and gated cleanup.
verify
Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.
retrospective
Perform a post-implementation retrospective analysis measuring spec adherence, implementation deviations, and lessons learned.
doctor
Validate project health: templates, agent config, Python runner/helpers, constitution, and feature artifacts.
validate
Verify spec-to-task traceability and check that completed tasks produced expected files.