القائمة
Compliance. Invoked as `$officer <question or audit request>`. Answers regulatory questions, audits codebase/architecture for privacy violations. Advisory only.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Cross-project build pipeline. Invoked as $wave-build <feature> or $wave-build with Pipeline/Task manifest/Wave args. Runs the full pipeline end to end including all git work.
Wave task runner. Reads a wave.md file and runs each pipeline sequentially. Invoked as `$wave <path/to/wave.md>`. Argument is the path to the wave manifest file.
Attributes Claude Code runtime token spend per sub-agent and per workflow run, parsed from local JSONL transcripts, and ranks the heaviest burners with estimated USD cost. Answers 'which agent burned the most tokens', 'what did this workflow/wave/pipeline cost', 'token breakdown', 'per-operation tokens', and any retrospective spend analysis. Triggered by 'token ledger', 'token attribution', 'heaviest token burner', 'which agent burned the most tokens', 'what did the run/workflow/wave cost', 'token breakdown', 'per-agent tokens', 'per-operation tokens'. Complements /pcm:context-meter: that audits STATIC context size, this covers RUNTIME spend attribution — route static-budget questions to context-meter, after-the-fact spend questions here.
Code hygiene audit — ghost fields, dead code, deps, arch, types, naming, quality. Domain-hydrated at install time.
Security deep scan — injection, auth, API, LLM/prompt, sensitive data, crypto, transport, supply-chain. Domain-hydrated at install time.
Exhaustive multi-angle analysis. Invoked by `360`, `three-sixty`, `do a 360`, "what could go wrong", or explicit blind-spot sweep requests.
| name | officer |
| description | Compliance. Invoked as `$officer <question or audit request>`. Answers regulatory questions, audits codebase/architecture for privacy violations. Advisory only. |
Read .claude/commands/officer.md in full — it is your complete role manual. Follow it verbatim.
Argument: compliance question, audit request, or architecture review.
docs/commands/officer/references/ directly for the full regulatory base. For latest developments not yet in the file, use WebSearch/WebFetch for narrow fact checks.RR, RRP, "research and report", "regulatory landscape", or another broad research task, execute the shared RR-compatible pipeline through .codex/skills/rr/SKILL.md instead of doing inline web research. For compliance topics, prefer primary regulatory sources and preserve uncertainty.