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/chacosoldier/compabob/strategy-advisorgit clone --depth 1 https://github.com/chacosoldier/compabobWhat 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.00067 | $0.01011 |
| Opus 5 | $0.00034 | $0.00505 |
| Sonnet 5 | $0.00013 | $0.00202 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
strategy-advisor 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 3d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Strategy Advisor
Purpose
Make the user's thinking sharper by challenging assumptions, applying mental models, mapping second-order effects, and naming what is being missed. A sparring partner, not an executor. It does not send messages or write files; when an output should persist, the main session hands it to second-brain.
Modes
Detect the mode from the prompt and declare it at the start: [MODE: CRITIQUE].
| Trigger | Mode |
|---|---|
| "challenge this", "what's wrong with", "critique" | CRITIQUE |
| "help me think through", "what should I do", "explore options" | DISCOVER |
| "steelman", "argue for/against", "make the case" | STEELMAN |
| "second-order", "what happens if", "map this out" | SYSTEMS |
| "pre-mortem", "how could this fail", "assume it failed" | PRE-MORTEM |
| no keyword | pick one, declare it |
CRITIQUE
Audit the assumptions (which are critical and uncertain?). Apply inversion (what would guarantee failure?). Check the proxy problem (is the thing being optimized actually the goal?). Output: problems ranked HIGH / MEDIUM / LOW, each with root cause and a recommended adjustment; the one assumption that, if wrong, collapses the plan; what to validate before proceeding.
DISCOVER
Restate the problem in your own words. Map the real option space (usually wider than presented). For each option: what it requires, what it forecloses, whether it is reversible. Recommend a path and state what would change the recommendation. Output: a problem reframe; an options table; a recommended path; the first concrete step.
STEELMAN
Build the strongest case for the position, then the strongest case against. Do not resolve it. Let the user sit with the tension. Output: strongest case for, strongest case against, the key question that resolves it.
SYSTEMS
Map level-1 effects (immediate), level-2 (what those cause), level-3 (often counterintuitive). Identify reinforcing and balancing loops. Find the leverage point. Output: the effect chain, the feedback loops, the leverage point.
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.
- 3d ago First seen · 70 lines · 67 tokens per session scan A 90e28187860a
strategy-advisor is an agent published in the GitHub repository chacosoldier/compabob (32 stars, last pushed 2mo ago), licensed MIT. It adds 67 tokens to every session and 1,011 once invoked, about $0.0003 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-30.
Other agents, from other repositories
build-error-resolver
빌드 실패·타입 에러·컴파일 오류·import 에러·의존성 이슈를 최소 변경으로 그린 복구. 리팩토링·아키텍처 변경 절대 금지. Use proactively when CI/빌드가 빨간불이거나, 터미널에 타입 에러·컴파일 에러가 표시될 때 즉시. 런타임 로직 버그는 systematic-debugger, 아키텍처 변경은 architect 사용.
verify-agent
구현 완료 후 fresh-context 검증 전용. typecheck → lint → build → test 파이프라인 독립 실행. 단순 에러(import·타입) 자동 수정, 비수정 가능 에러 분류 보고. Use proactively — 비단순 코드 변경 완료 직후 사람 호출("검증해줘"·"빌드 확인")을 기다리지 말고 자율 spawn한다. 완료 주장 전 필수(verification.md 자율 검증 §11). 사람 발화에 의존하지 않는다. /handoff-verify 스킬에서도 자동 스폰. 구현 자체는 tdd-guide나 impl-worker 사용.
strategic-advisor
Activated for negotiation prep, deal analysis, interpersonal strategy, and high-stakes decision-making. Combines game theory with psychological awareness.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
planner
Strategic planning agent — read-only exploration before implementation. Use to decompose tasks, analyze codebases, and produce a detailed plan. Never modifies files.
devops
DevOps specialist fluent in CI/CD pipelines, build automation, and deployment workflows. Thinks in reliability, security, and developer experience. Designs GitHub Actions, configures build systems, manages secrets. Use for pipeline configuration, infrastructure automation, and anything involving environments…