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/AutomateLab-tech/agency-osWrote 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/automatelab-tech/agency-os/approve)<a href="https://agentmods.dev/commands/automatelab-tech/agency-os/approve"><img src="https://agentmods.dev/badge/commands/automatelab-tech/agency-os/approve.svg" alt="Measured on agentmods" 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.00200 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
approve 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 6d 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.
What it actually says
Command: approve <id>
Promote a task from Discussion -> To-Do, cascading active children. Requires explicit user authorization for the specific row or batch (see "Authorization gates" in SKILL.md) — approve is a Gate-1 transition, never run it on the orchestrator's initiative.
- Sync preflight.
- Resolve
<id>. Verify status isDiscussion(orSuggestion— fast-track allowed). Refuse otherwise. - Cascade: collect every descendant with status in
{Suggestion, Discussion}. For each, set Status -> To-Do. - Set the parent's Status -> To-Do. If
--priorityprovided, set on the parent only. - Append a
### <date> — approvedentry to the parent's Discussion log. - Print:
-> To-Do: [<title>](<url>) (cascaded N subtasks).
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.
- 6d ago First seen · 11 lines · 0 tokens per session scan A be4e3c633a84
approve is a command published in the GitHub repository AutomateLab-tech/agency-os (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 200 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
p9
A Tech Lead mode for writing prompts and managing the P8 team. A Tech Lead guides technical work and breaks projects into tasks.
survey
An interactive seven-part questionnaire for collecting user feedback about PUA. A questionnaire is a structured set of questions answered by a user.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
kpi
A report card that generates a level and performance report.
sdd
Generate a Kiro-style spec triple — specs/ /{requirements,design,tasks}.md.