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/create-plan)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/create-plan"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/create-plan/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/create-plan"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/create-plan.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.01313 |
| Opus 5 | $0.00000 | $0.00656 |
| Sonnet 5 | $0.00000 | $0.00263 |
| Haiku 4.5 | $0.00000 | $0.00131 |
Grade A, and why
create-plan 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Create a detailed implementation plan for changes to this workspace. Plans are thorough documents that capture the full context, rationale, and step-by-step tasks needed to execute a change with complete alignment across the project.
Variables
request: $ARGUMENTS (describe what you want to plan — new command, new workflow, structural change, template update, etc.)
Instructions
- IMPORTANT: You are creating a PLAN, not implementing changes. Research thoroughly, think deeply, then output a comprehensive plan document.
- Use your reasoning capabilities to think hard about the request, workspace structure, and best approach.
- Research the workspace to understand existing patterns, conventions, and how this change fits.
- Create the plan in the
plans/directory with filename:YYYY-MM-DD-{descriptive-name}.md- Use today's date
- Replace
{descriptive-name}with a short, kebab-case name (e.g., "add-guest-research-command", "restructure-outputs", "create-outreach-workflow")
- Fill out every section of the Plan Format below. Replace all
<placeholders>with specific, actionable content. - Be thorough — this plan will be executed by
/implementand needs enough detail to execute without ambiguity. - Follow existing patterns. Study similar files in the workspace before proposing new structures.
Research Phase
Before writing the plan, investigate:
-
Read core reference files:
CLAUDE.md— workspace overviewcontext/— background context on the user and project
-
Explore relevant areas:
- If creating a command: read existing commands in
.claude/commands/ - If modifying outputs: explore
outputs/structure and examples - If updating templates: check
reference/for existing patterns - If adding scripts: review
scripts/for conventions
- If creating a command: read existing commands in
-
Understand connections:
- How does this change relate to existing workflows?
- What files reference or depend on areas being changed?
- Are there naming conventions to follow?
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 · 234 lines · 0 tokens per session scan A 0eab7f341e2e
create-plan 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 1,313 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.