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/board)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/board"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/board/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/board"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/board.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.00994 |
| Opus 5 | $0.00000 | $0.00497 |
| Sonnet 5 | $0.00000 | $0.00199 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
board 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 11d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board — Convene Department Leads
Bring 2-4 Department Leads together for a cross-functional decision. Each speaks in sequence. you synthesizes and decides.
Variables
decision: (the decision, question, or situation you need Department Leads to weigh in on)
Instructions
You are convening your Department Leads. This command is for decisions that cross departmental boundaries — where you need multiple perspectives before moving forward.
Use /board when:
- A decision affects multiple departments (revenue + capacity + finance)
- A strategic question needs honest input from different lifecycle perspectives
- you is at a fork and needs department-level counsel, not just analysis
Use /team when:
- The question clearly belongs to one department
- You need execution, not strategy
Step 1: Identify the Decision
Read the request. Determine:
- What is the core decision to be made?
- Which departments have a stake in it?
- What context is needed (pipeline data, capacity, financial model, positioning)?
Step 2: Select the Board
Choose 2-4 Department Leads whose domains are directly relevant. Standard combinations:
| Decision Type | Board Members |
|---|---|
| New client acceptance | Retain & Deliver Lead (capacity), Finance Lead (profitability), Convert Lead (pipeline fit) |
| Pricing decision | Finance Lead (margin), Convert Lead (market fit), Attract Lead (positioning) |
| Strategic ICP pivot | Attract Lead (messaging/ICP), Convert Lead (pipeline impact), Finance Lead (revenue model) |
| New build vs. buy | AI HR Lead (technical), Finance Lead (cost), Retain & Deliver Lead (operational impact) |
| Content strategy shift | Attract Lead (brand), Convert Lead (sales signal), Finance Lead (ROI) |
| Capacity vs. growth | Retain & Deliver Lead (delivery), Finance Lead (numbers), Convert Lead (pipeline) |
You are always the decision-maker — the board informs, not governs.
Step 3: Load Context
Before each Lead speaks, read their role file:
team/attract/lead.mdteam/convert/lead.mdteam/retain-deliver/lead.mdteam/ascend/lead.mdteam/finance/lead.mdteam/ai-hr/lead.md
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.
- 11d ago First seen · 137 lines · 0 tokens per session scan A f2de8337d2bd
board 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 994 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
status
Display project status, active tracks, and next actions.
discuss
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.