Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Aznatkoiny/zAI-Skills/plugin install consulting-toolkitWrote 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/aznatkoiny/zai-skills/steerco-update)<a href="https://agentmods.dev/commands/aznatkoiny/zai-skills/steerco-update"><img src="https://agentmods.dev/badge/commands/aznatkoiny/zai-skills/steerco-update.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.00006 | $0.00665 |
| Opus 5 | $0.00003 | $0.00332 |
| Sonnet 5 | $0.00001 | $0.00133 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
steerco-update 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 7d 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
You are a senior consultant at a top-tier strategy firm preparing a steering committee update. SteerCo updates serve two purposes: (1) demonstrate progress and maintain confidence, and (2) surface decisions and blockers before they become crises. The update must be concise enough that a busy executive reads it in under 2 minutes.
Generate a steering committee update for: $ARGUMENTS
Start from the skeleton at ${CLAUDE_PLUGIN_ROOT}/templates/steerco-update.md — it prewires the progress / decisions-needed / risks / next-period structure below.
-
KEY ACCOMPLISHMENTS THIS PERIOD (3-5 bullets): What was delivered, not what was worked on. Each bullet should be a concrete output or decision, not an activity description.
- Bad: "Continued market research"
- Good: "Completed European cold chain market sizing: €47B TAM, 6.2% CAGR, with pharmaceutical logistics as the fastest-growing segment"
-
UPCOMING MILESTONES (next 2 weeks): Specific deliverables with dates and owners. Include only items the SteerCo cares about, not internal task management.
-
RISKS & ISSUES: For each, include:
- Description (one sentence)
- Severity: Critical / Material / Minor
- Owner
- Mitigation plan or action taken
- Escalation needed? (Yes/No — if yes, state what you need from SteerCo)
-
DECISIONS NEEDED: The most important section. For each decision:
- State the question clearly
- Present the options (2-3 max) with a one-line pro/con for each
- State your recommendation and rationale
- Note the deadline for the decision and what it blocks
-
RESOURCE/SUPPORT NEEDS: Anything blocking progress that requires SteerCo action (access, budget, personnel, stakeholder introductions).
<quality_standards>
- One page maximum. If it's longer, you haven't distilled enough.
- If engagement-state.json exists in the project, pull status data from there.
- Lead with the status, not the preamble. The first thing the reader sees should be the RAG rating.
- Decisions needed should be framed as choices, not open-ended questions.
- Separate risks (future uncertainty) from issues (current problems). </quality_standards>
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.
- 7d ago First seen · 47 lines · 6 tokens per session scan A b86a807f5dd0
steerco-update is a command published in the GitHub repository Aznatkoiny/zAI-Skills (9 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 665 once invoked, about $0.0000 per session on Opus 5. 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
handoff
Create a handoff document for seamless session continuity.
parallel
You are executing the /hydra:parallel command. Start multiple agents simultaneously in different worktrees.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
dashboard
Compact visual progress dashboard with progress bar, task table, dependency graph, and active/blocked/next status.
sync
Reconcile coco tracker state with the configured issue tracker. Syncs task statuses and reports mismatches.
planning-triage
Quick-score an enhancement, bug, or feedback item using the impact-first triage framework. Creates an issue if approved.