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/conorbronsdon/agent-context-os/content-shippedgit clone --depth 1 https://github.com/conorbronsdon/agent-context-osWrote 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/conorbronsdon/agent-context-os/content-shipped)<a href="https://agentmods.dev/commands/conorbronsdon/agent-context-os/content-shipped"><img src="https://agentmods.dev/badge/commands/conorbronsdon/agent-context-os/content-shipped.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.00022 | $0.00361 |
| Opus 5 | $0.00011 | $0.00180 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
content-shipped 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 today.
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.
What it actually says
content-shipped — Log Shipped Content
Use after publishing anything: a blog post, social post, newsletter issue, video clip, or any other content piece.
Instructions
1. Gather metadata
Ask for (or infer from context):
- Date — today's date (run
date +%Y-%m-%dif not provided) - Type — e.g.:
blog-post,linkedin-post,newsletter,video,episode,clip,other - Title / Description — post title, hook, or short description
- Platform — where it was published
- Link — URL if available; use
TBDif not yet live - Notes — any additional context worth remembering
2. Add the entry to content/log.md
Append the row as the last line of the table.
| {Date} | {Type} | {Title/Description} | {Platform} | {Link} | {Notes} |
A fresh log has no data rows, so the table's last line is the dashed separator row — put the first entry directly beneath it. Every later row goes beneath the previous one. Never insert above the separator; that breaks the table.
3. Confirm
One line: "Logged: {type} — {title/description}"
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.
- today Changed 8702952b16c6
- 5d ago First seen · 38 lines · 22 tokens per session scan A ad7c86206b49
content-shipped is a command published in the GitHub repository conorbronsdon/agent-context-os (22 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 361 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-30.
Other commands, from other repositories
cm-connect
Hook this repo and another to the shared memory layer end to end — survey, operator-confirmed enrollment, an optional shared fact, absorption both ways, and the network payoff.
cm-doctor
Print the resolved StoreContext (native/canonical/control-plane paths, enrollment, registry health).
generate-docs
Generates a Rust-scoped symbol inventory to assist agents in understanding the public API surface of the workspace.
extensions
Show what the connected context expects to reach, and whether this machine provides it.
list
List the NeatContext contexts you can connect.
ctx
Experimental integration for ctx in Cursor.