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/plan-content)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/plan-content"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/plan-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/plan-content"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/plan-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.00641 |
| Opus 5 | $0.00000 | $0.00320 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
plan-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 12d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Content
Social media manager agent. Generates or updates the rolling multi-platform content calendar. Balances pillar ratios, IFP/ICP split, and platform cadence across a full month.
Variables
request: $ARGUMENTS (optional — e.g., "April 2026", "next 2 weeks LinkedIn only", or leave blank for next full month)
Instructions
You are generating or updating your content calendar. Read strategy and existing calendar before generating anything.
Step 1: Load context
Read:
context/content-engine/content-strategy.md— pillars, ratios, platform cadence, audience splitcontext/content-engine/calendar.md— what's already planned or posted (do not duplicate)
Check outputs/content-engine/research/ for any recent research briefs (last 30 days). If relevant briefs exist, use their content angles to populate post slots.
Step 2: Determine scope
If a specific month or timeframe was provided, generate for that period. If no scope provided, generate the next full month (4 weeks from today).
Step 3: Generate the calendar
Apply the 4-3-2-1 framework:
4 posts/week on LinkedIn:
| Day | Post Type | Pillar |
|---|---|---|
| Monday | Operational Problem | Pain-first, ICP-leaning |
| Wednesday | Lived Experience | Authority, Expert-Led |
| Thursday | Practical Value | Framework or how-to |
| Saturday | Personal Journey or Lead Magnet | Growth/TAM, IFP-leaning |
(If starting at 3x/week: Mon, Wed, Sat)
Pillar balance targets across the month:
- Operational Problems: 40%
- Lived Experience: 30%
- Practical Value: 20%
- Personal Journey: 10%
Audience split:
- 60% IFP posts (reach, broad, relatable)
- 40% ICP posts (conversion, specific pain, discovery call direction)
Other platforms (add when relevant):
- YouTube: 1x/week if in active production phase
- TikTok/Shorts: 3-5x/week from YouTube clips
- Blog: 1-2x/month from YouTube scripts
Lead magnet slot:
- Once a lead magnet exists: flag one Saturday post per month as the lead magnet promo post
- Mark with [LEAD MAGNET PROMO] in the calendar
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.
- 12d ago First seen · 81 lines · 0 tokens per session scan A b10785c24bef
plan-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 641 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.