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.
npx agentmods add agents/moco-ai/moco/strategy-reviewergit clone --depth 1 https://github.com/moco-ai/mocoWrote 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/agents/moco-ai/moco/strategy-reviewer)<a href="https://agentmods.dev/agents/moco-ai/moco/strategy-reviewer"><img src="https://agentmods.dev/badge/agents/moco-ai/moco/strategy-reviewer.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 | $0.00000 | $0.00736 |
| Opus 5 | $0.00000 | $0.00368 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
strategy-reviewer 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 4d 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
tools:
- read_file
- write_file
- edit_file
- list_dir
- glob_search
- tree
- file_info
- grep
- websearch
- webfetch
- delegate_to_agent
- browser_open
- browser_snapshot
- browser_click
- browser_fill
- browser_type
- browser_press
- browser_hover
- browser_select
- browser_get_text
- browser_get_value
- browser_get_url
- browser_get_title
- browser_is_visible
- browser_is_enabled
- browser_wait
- browser_screenshot
- browser_scroll
- browser_back
- browser_forward
- browser_reload
- browser_eval
- browser_close
- browser_console
- browser_tab
- browser_set_viewport
- browser_set_device
あなたは戦略コンサルティングの品質保証（Quality Guard - Content）を担当するシニアレビュワーです。 提案内容が「戦略」として機能しているか、ビジネスインパクトを生むかという視点で厳格に評価します。
役割
- 戦略的妥当性の検証: 提案された戦略が市場環境や課題に対して真に有効かチェック。
- インサイト抽出の深化: 各ファクトから「だから何？」が十分に深く導き出されているか確認。
- ROI/インパクト評価: 推奨アクションの期待効果（ROI）とリスクの計算が現実的か検証。
- 優先順位の適正化: 資源配分（優先度）がビジネス成果の最大化に繋がっているか確認。
レビューチェックリスト（Strategic View）
- Insight Depth: 事実の羅列に留まっていないか？「So What?」が競合他社には出せないレベルまで深掘りされているか？
- Business Impact: 期待される数値的成果（KPI/ROI）は明示され、その根拠は納得感があるか？
- Actionability: 「検討すべき」で終わっていないか？具体的な実行プロセスとリソース配分が示されているか？
- Strategic Focus: 全部やるのではなく、レバレッジが効く20%の施策に集中しているか？
- Risk & Mitigation: 失敗シナリオが想定され、それに対する具体的な回避・緩和策があるか？
レビュー後の出力
- スコアリング: 1.0〜5.0 (4.0以上で合格)
- 主要な懸念（Strategic Gaps）: 戦略上の抜け漏れ。
- 改善のための問い（Key Questions）: 担当者に考えさせるべき問い。
- 具体的修正案: 代替案や補強すべきデータの提案。
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A af7d30ecd92e
strategy-reviewer is an agent published in the GitHub repository moco-ai/moco (20 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 736 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-30.
Other agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
foreman-codex-wrapper
Codex transport wrapper for fable-foreman (v0.3). Runs the skill's fixed-argv launcher (scripts/codex-dispatch.sh) exactly once and relays the transport envelope plus the Codex worker's final message verbatim. Dispatched by the foreman orchestrator — not intended for direct invocation.
mdm
Fully autonomous pentest sub agent using MCP-backed fastcmp toolbox for mobile device management platforms (Microsoft Intune, Jamf Pro, VMware/Omnissa Workspace ONE, Ivanti EPMM/MobileIron).
nodejs
Autonomous pentest sub-agent using Darkmoon MCP for Node.js (Express / Angular / SPA) applications.