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 skills add daehounan/agency-agents-fork --skill strategy-nexusgit clone --depth 1 https://github.com/daehounan/agency-agents-forkWrote 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/skills/daehounan/agency-agents-fork/strategy-nexus)<a href="https://agentmods.dev/skills/daehounan/agency-agents-fork/strategy-nexus"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/strategy-nexus/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/daehounan/agency-agents-fork/strategy-nexus"><img src="https://agentmods.dev/badge/skills/daehounan/agency-agents-fork/strategy-nexus.svg" alt="Reviewed on agentmods" width="80" 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.00137 | $0.00611 |
| Opus 5 | $0.00068 | $0.00305 |
| Sonnet 5 | $0.00027 | $0.00122 |
| Haiku 4.5 | $0.00014 | $0.00061 |
Grade A, and why
strategy-nexus 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 12d 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
NEXUS Strategy Orchestration Skill
When this skill activates, route the user to the appropriate NEXUS playbook based on engagement type and phase.
Top-level entry points
| User signal | Playbook to load |
|---|---|
| "Where do I start?" / "how do I run an engagement?" | strategy/QUICKSTART.md |
| "Give me the executive view" | strategy/EXECUTIVE-BRIEF.md |
| "Walk me through the full doctrine" | strategy/nexus-strategy.md |
Phase playbooks (sequential)
| Phase | Focus | Playbook |
|---|---|---|
| 0 | Intelligence & Discovery | strategy/playbooks/phase-0-discovery.md |
| 1 | Strategy & Architecture | strategy/playbooks/phase-1-strategy.md |
| 2 | Foundation & Scaffolding | strategy/playbooks/phase-2-foundation.md |
| 3 | Build & Iterate | strategy/playbooks/phase-3-build.md |
| 4 | Quality & Hardening | strategy/playbooks/phase-4-hardening.md |
| 5 | Launch & Growth | strategy/playbooks/phase-5-launch.md |
| 6 | Operate & Evolve | strategy/playbooks/phase-6-operate.md |
Named scenarios (cross-phase)
| Scenario | Runbook |
|---|---|
| Startup MVP shipping | strategy/runbooks/scenario-startup-mvp.md |
| Enterprise feature delivery | strategy/runbooks/scenario-enterprise-feature.md |
| Marketing campaign launch | strategy/runbooks/scenario-marketing-campaign.md |
| Production incident response | strategy/runbooks/scenario-incident-response.md |
Coordination assets
- Agent activation prompts:
strategy/coordination/agent-activation-prompts.md - Handoff templates:
strategy/coordination/handoff-templates.md
When NOT to use
- Single-agent task → call the agent directly
- Tactical question (one phase only) → load that one phase playbook
- Lightweight planning → use
ecc:plannerorecc:planinstead
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.
- 12d ago First seen · 49 lines · 137 tokens per session scan A 266a4dee88cc
strategy-nexus is a skill published in the GitHub repository daehounan/agency-agents-fork (2 stars, last pushed 3mo ago), licensed MIT. It adds 137 tokens to every session and 611 once invoked, about $0.0007 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 skills, from other repositories
cognito
AWS Cognito user authentication and authorization service. Use when setting up user pools, configuring identity pools, implementing OAuth flows, managing user attributes, or integrating with social identity providers.
sns
AWS SNS notification service for pub/sub messaging. Use when creating topics, managing subscriptions, configuring message filtering, sending notifications, or setting up mobile push.
iam
AWS Identity and Access Management for users, roles, policies, and permissions. Use when creating IAM policies, configuring cross-account access, setting up service roles, troubleshooting permission errors, or managing access control.
i18n-parity
MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use automatically (without being asked) whenever you add or change…
dag-map
Render the multi-agent orchestration DAG for a session — parent→child subagent edges, tree depth, and fan-out — from the Agent Monitor workflow intelligence API. Cross-checks the orchestration dataset against the raw agent records and session detail. Use when visualizing how a session's agent structure was organized.
update-project-docs
MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features. Use automatically (without being asked) at the end of ANY change-set that adds or alters an env var, event type, hook…