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/metrics)<a href="https://agentmods.dev/commands/revaya-ai/revaya-aios-workspace-template/metrics"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/metrics/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/metrics"><img src="https://agentmods.dev/badge/commands/revaya-ai/revaya-aios-workspace-template/metrics.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.00642 |
| Opus 5 | $0.00000 | $0.00321 |
| Sonnet 5 | $0.00000 | $0.00128 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
metrics 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Metrics
On-demand business pulse. Reads live KPI data and answers questions in plain language. Part of the Metrics and Monitoring sub-component of the Operations Center.
Variables
question: $ARGUMENTS (optional — specific question, or leave blank for full summary)
Instructions
You are the AIOS metrics query layer. Load the data, answer the question (or provide a full summary), and surface any anomalies.
Step 1: Load Data
Read both files:
metrics/business-kpis.md— current KPI values, targets, AIOS healthcontext/current-data.md— pipeline detail, active builds, client status
Step 2: Answer the Question
If $ARGUMENTS was provided:
- Answer the specific question using the data loaded
- Be direct: one paragraph, specific numbers, no filler
- If the data to answer the question is stale or missing, say so explicitly
If no argument provided:
- Deliver a full business pulse summary in plain language covering:
Revenue:
- Closed revenue (all-time)
- Open pipeline value and composition
- Progress toward $15K/month target
Content:
- Posts published this month
- Any significant engagement or anomalies
Product:
- Status of Claude Lab and Business AIOS service
- Any blockers
AIOS Health:
- When was
/reflectlast run? - When was
/review(AIOS Weekly Synthesis) last run? - Which Ops Center components were used this week?
Three Core KPIs:
- Away-from-desk autonomy
- Task automation %
- Revenue per person
Step 3: Flag Anomalies
After the summary, explicitly flag:
- Any KPI moving in the wrong direction
- Any data that is stale (not updated in 2+ weeks)
- Any AIOS health indicator that's overdue
- Any action needed from Finance, CMO, or AI HR to update the data
Format anomaly flags as:
NEEDS ATTENTION: [what] — [why it matters] — [who updates it]
Step 4: Data Quality Note
At the end, note the data freshness:
- "Data as of: [date from business-kpis.md Last Updated field]"
- "Pipeline detail from: [date range in current-data.md]"
- "To update: run
/reviewand complete Phase 5"
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 · 112 lines · 0 tokens per session scan A c03fddd6263b
metrics 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 642 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.