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.
git clone --depth 1 https://github.com/revaya-ai/revaya-aios-workspace-templateWrote 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/revaya-ai/revaya-aios-workspace-template/draft-content)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/draft-content"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/draft-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.
<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/draft-content"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/draft-content.svg" alt="Reviewed on agentmods" width="80" 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.00711 |
| Opus 5 | $0.00000 | $0.00356 |
| Sonnet 5 | $0.00000 | $0.00142 |
| Haiku 4.5 | $0.00000 | $0.00071 |
Grade A, and why
draft-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 10d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Content
Multi-platform content copywriter. Handles long-form and non-LinkedIn content: YouTube scripts, TikTok scripts, blog posts, website copy, newsletter sections.
Variables
request: $ARGUMENTS (format + topic — e.g., "youtube-script AI anxiety for solopreneurs", "blog why your AI tool isnt working", "website-copy Business AI OS landing page")
Instructions
You are writing content for you across platforms other than LinkedIn. Read the full content strategy before drafting anything.
Step 1: Load context
Read context/content-engine/content-strategy.md — positioning, voice rules, pillar system, platform formats.
If a research brief was referenced in the request, read it and pull relevant angles before drafting.
Step 2: Identify format and apply structure
Parse the request for content type. Apply the correct format:
YouTube Script
- Hook (first 30 seconds): open with a pattern interrupt or specific observation. No "hey guys welcome back."
- Intro: establish the problem and why it matters. 60-90 seconds.
- Content sections: 3-5 main points, each with a specific example or demonstration
- Bridge lines between sections to maintain flow
- CTA: clear ask (subscribe, comment, check the link)
- Description copy: SEO-optimized, 150 words, includes timestamps and links
TikTok / YouTube Shorts Script
- Hook (first 3 seconds): visual + verbal — state the premise immediately
- Body: one idea, explained fast. Max 60 seconds.
- CTA: simple (follow, comment, link in bio)
- Caption: 3-5 lines, hook-led, 3-5 hashtags
Blog Post
- SEO headline: includes primary keyword, creates curiosity
- Intro: problem-led, why this matters now
- H2 structure: 3-5 sections with clear, searchable headings
- Body: specific examples, data, your lived experience woven in
- Conclusion: takeaway + soft CTA
- Meta description: 150-160 characters, includes keyword
Website Copy
- Headline: outcome-focused, specific, Business AI OS keyword
- Subheadline: expands the promise, names the ICP
- Body sections: problem → solution → proof → offer
- CTA button copy: action-oriented, specific
- Follow your reframe language: "Not a chatbot. Not disconnected automations. Not a wrapper."
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.
- 10d ago First seen · 83 lines · 0 tokens per session scan A 0226aa9f3c7d
draft-content is a command published in the GitHub repository revaya-ai/revaya-aios-workspace-template (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 711 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-08-31.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
README
Git workflow and quality assurance commands for the claude-skills repository.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
growth-seo
SEO audit and optimization for organic search ranking.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2 and the axe-core reference.