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/openvidu/openvidu.io/publish-postgit clone --depth 1 https://github.com/OpenVidu/openvidu.ioWrote 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/openvidu/openvidu.io/publish-post)<a href="https://agentmods.dev/commands/openvidu/openvidu.io/publish-post"><img src="https://agentmods.dev/badge/commands/openvidu/openvidu.io/publish-post.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.00015 | $0.00338 |
| Opus 5 | $0.00008 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
publish-post 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 6d 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.
What it actually says
Publish the draft blog post whose slug is $ARGUMENTS. This is the mechanical draft→publish
transition defined in .claude/skills/blog-write/references/conventions.md.
- Locate the draft at
docs/blog/posts/YYYY/MM/<slug>.md(literalYYYY/MMdirectories). If it is not there, stop and tell the user — the post may already be published or the slug wrong. - Take today's date as the publish date (
<year>, zero-padded<month>). - Set the frontmatter
date:to the publish date. - In the post body, string-replace every
YYYY/MM/with<year>/<month>/— this rewrites the asset references and nothing else, by design. git mv docs/blog/posts/YYYY/MM/<slug>.md docs/blog/posts/<year>/<month>/<slug>.mdandgit mv docs/assets/images/blog/YYYY/MM/<slug> docs/assets/images/blog/<year>/<month>/<slug>(create the year/month directories if this is the first post of the month).- Verify nothing else remained in the placeholder folders; remove them if now empty.
- Run
ovweb lint docs/blog/posts/<year>/<month>/<slug>.mdand fix any error it reports. - Remind the user: merging this to
maindoes not put the post online — it goes live with the next Publish Web workflow run (ovweb publish latest X.Y).
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.
- 6d ago First seen · 22 lines · 15 tokens per session scan A d194544e57ae
publish-post is a command published in the GitHub repository OpenVidu/openvidu.io (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 338 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.