agentmods.dev

openstart: Command for Claude Code

.claude/commands/content.md

content is a command for Claude Code from vijayatechlabs/openstart. It costs 20 tokens per session (513 once invoked), scanned A, original, MIT.

A command that turns a shipped customer-facing feature into a reviewable brief for a blog post or pull request. It follows the project's defined handoff process and can place the brief in a local content inbox.

In plain words
What is it for?
Use it after releasing a new feature, major improvement, or launch to record the audience, topic angle, and search keyword for the related content work.
Why use it?
It prevents marketing content from being forgotten after a feature ships and keeps internal changes from being treated as launch material. It also makes external publishing a deliberate, reviewable step.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is vijayatechlabs/openstart's own configuration. It tells Claude Code how to work on openstart itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything openstart configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is bash .ai/framework/content.sh "<what shipped>" [--audience "<who>"] [--angle "<hook>"] [--keyword "<seo term>"].

not rated 5repo 2mo ago A scan 20 tokens original MIT
View source ↗ vijayatechlabs/openstart vijayatechlabs.com
Reuse

Borrowing it

Nothing to install: this file belongs to vijayatechlabs/openstart. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vijayatechlabs/openstart/main/.claude/commands/content.md
Clone the repo
git clone --depth 1 https://github.com/vijayatechlabs/openstart

Made for: Claude Code.

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.

agentmods badge for content

README.md
[![agentmods](https://agentmods.dev/badge/commands/vijayatechlabs/openstart/content/github.svg)](https://agentmods.dev/commands/vijayatechlabs/openstart/content)
Your own site
<a href="https://agentmods.dev/commands/vijayatechlabs/openstart/content"><img src="https://agentmods.dev/badge/commands/vijayatechlabs/openstart/content/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.

agentmods 80×15 button for content

Your own site · 80×15
<a href="https://agentmods.dev/commands/vijayatechlabs/openstart/content"><img src="https://agentmods.dev/badge/commands/vijayatechlabs/openstart/content.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 513 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00513
Opus 5.5 $0.00008 $0.00205
Sonnet 5.5 $0.00004 $0.00103
Haiku 4.5 $0.00002 $0.00051

Measured 2mo ago against content hash 4147d8750839, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

content 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 2mo 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.

.claude/commands/content.md · 45 lines

What it actually says

You are running the OpenStart content handoff for the current project.

Follow .ai/framework/CONTENT-HANDOFF.md exactly. It is the canonical description of the ship → blog pipeline.

When to run

Only for user-facing / marketable changes — a new feature, a notable improvement, a launch. Skip internal refactors, infra, and most bug fixes (those go in CHANGELOG.md only). This is step 5 of the Definition of Done (AGENT-GUIDE.md §10).

Steps

  1. Run the capture script with what shipped and any angle the user gave:

    bash .ai/framework/content.sh "<what shipped>" [--audience "<who>"] [--angle "<hook>"] [--keyword "<seo term>"]

    If the user didn't specify audience/angle/keyword, infer sensible values from the change and pass them — but never invent a feature that didn't ship.

  2. Show the output — the local brief path, where it was delivered, and the brief text — so the user can review.

  3. Ask before any external write. In Local mode the brief is just written to the blog's CONTENT-INBOX.md — no confirmation needed. In GitHub mode, do NOT run gh issue create automatically (external write, AGENT-GUIDE.md §9). Ask:

    "Shall I file this brief as a content issue on <blog-repo>?"

  4. If confirmed (GitHub mode), run the gh issue create one-liner that content.sh printed and report the returned issue URL.

Notes

  • The blog target is configured once in .ai/docs/CONTENT-PIPELINE.md: **Content path:** ../blog (Local) or **Content repo:** owner/blog (GitHub). The CONTENT_DIR / CONTENT_REPO env vars override it for one-offs. If neither is set, tell the user how to set the line; the brief is still logged locally.
  • The brief is a seed — the actual post is written in the blog/content project following the AEO framework.
Changes

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.

  1. 2mo ago First seen · 45 lines · 20 tokens per session scan A 4147d8750839

Subscribe to this mod's changes

content is a command published in the GitHub repository vijayatechlabs/openstart (5 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 513 once invoked, about $0.0001 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.

Marketing and SEOWriting and docsaeo
Related

content compared with commands from other repositories

content next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
contentvijayatechlabs/openstartCommand52mo agoMITA20Claude Code
geomverab/eGEOagentsCommand217yesterdayMITA21Claude Code
create-topicakii-technologies-ltd/akii-seo-ai-search-optimizerCommand794d agoMITA18Claude Code
publishindranilbanerjee/contentforgeCommand318d agoMITA20Claude Code
rankHouseofmvps/claude-rankCommand1494mo agoMITA21Claude Code
new-monthindranilbanerjee/neels-pluginsCommand78d agoMITA35Claude Code
citationsshalintripathi/organic-osCommand71mo agoMITA15Claude Code