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/review)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/review"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/review/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/review"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/review.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.01818 |
| Opus 5 | $0.00000 | $0.00909 |
| Sonnet 5 | $0.00000 | $0.00364 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
review 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review
GTD Weekly Review + AIOS Weekly Synthesis — Learning Loops cadence 2 of 5. Processes inbox, walks through all project/action lists, scans areas and someday-maybe, rebuilds the dashboard, and runs a structured AIOS health check. Run weekly (Fridays recommended). Target: 45-75 minutes.
Instructions
You are running a GTD weekly review. This is the most important habit in the system — it keeps the GTD files trustworthy and complete. Follow the phases below interactively.
Phase 1: Load Context
Read all GTD files:
gtd/dashboard.md— Current state overviewgtd/inbox.md— Items to processgtd/projects.md— Master project listgtd/next-actions.md— Actions by contextgtd/waiting-for.md— Delegated itemsgtd/someday-maybe.md— Back-burner ideasgtd/areas.md— Areas of responsibilitygtd/review-checklist.md— Review protocol and trigger lists
Phase 2: GET CLEAR
Goal: Empty all inboxes and capture everything floating in your head.
2.1 Process Inbox
- Read
gtd/inbox.md - If items exist, walk through each one using the GTD decision tree
- Route each item to the correct GTD file
- Empty inbox to zero
2.2 Mind Sweep
- Present the trigger list categories from
gtd/review-checklist.md - Go through each category — ask "Any open loops here?"
- Capture everything new to inbox, then process it
STOP after GET CLEAR and confirm before proceeding.
Phase 3: GET CURRENT
Goal: Ensure all lists reflect reality. Every project has a next action.
3.1 Review Calendar
- Ask about the past week: any follow-ups needed?
- Ask about the next 2 weeks: any preparation needed?
3.2 Walk Through Next Actions
- Present each context section from
gtd/next-actions.md - For each action: "Done? Still relevant? Needs updating?"
- Mark completed, remove stale, add new
3.3 Walk Through Waiting For
- Present each item from
gtd/waiting-for.md - Flag anything overdue — suggest follow-up
- Move received items to Completed section
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 · 183 lines · 0 tokens per session scan A 02501ea35cf4
review 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,818 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
trellis-finish-work
Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.
dashboard-session-unhide
Unhide a previously hidden session. Usage /dashboard:session-unhide.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
ops
Weekly operations loop — triage the inquiry inbox, advance the CRM pipeline, sweep open PRs across repos, and surface the content plan. Loads the ops skill.
tldr-help
Quick reference card for tldr modes, slash commands, and triggers.