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 easyinplay/harnessed --skill strategicgit clone --depth 1 https://github.com/easyinplay/harnessedWrote 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/easyinplay/harnessed/strategic)<a href="https://agentmods.dev/skills/easyinplay/harnessed/strategic"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/strategic.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.00147 | $0.01084 |
| Opus 5 | $0.00073 | $0.00542 |
| Sonnet 5 | $0.00029 | $0.00217 |
| Haiku 4.5 | $0.00015 | $0.00108 |
Grade A, and why
discuss-strategic 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
discuss-strategic workflow (v3)
Overview
3-phase sub-workflow mapping CLAUDE.md "Stage ①.a 战略层 — 新功能启动前强制 🔒" onto harnessed runtime (Phase v3.0-3.4 W0.1 — D-04 Stage ① Discuss 三层 + D-12 gstack 治理关卡 + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability / invokes | gate / artifacts |
|---|---|---|---|---|---|
| 1 | 01-office-hours |
gstack | opus | {{ capabilities.gstack-office-hours.cmd }} |
gate: judgments.strategic-gate.office-hours.fires |
| 2 | 02-plan-ceo-review |
gstack | opus | {{ capabilities.gstack-plan-ceo-review.cmd }} |
gate: judgments.strategic-gate.plan-ceo-review.fires |
| 3 | 03-persist |
planning-with-files | haiku | {{ capabilities.planning-with-files.cmd }} + invokes: /plan |
artifacts_expected: [findings.md] |
Capability refs
Sister workflows/capabilities.yaml entries:
gstack-office-hours— Bucket 3 治理关卡 (impl: gstack, cmd: /office-hours)gstack-plan-ceo-review— Bucket 3 治理关卡 (impl: gstack, cmd: /plan-ceo-review)planning-with-files— Bucket 4 核心 capability (impl: claude-code-plugin, cmd: /plan)
Gate refs
Sister workflows/judgments/strategic-gate.yaml:
office-hours.fires—phase.type in ['new_project', 'new_milestone', 'new_feature']plan-ceo-review.fires—phase.type == 'new_project' or phase.is_major_release == true
Invocation
- Slash command:
/discuss-strategic <text>(afterharnessed setup)
Routing rules
跳过条件 (sister CLAUDE.md "战略层 ❌ 跳过"):
- bug 修复 / 技术债 / 实现细节
- scope 已在历史
.planning/或 design doc 定义 - continuing 已有 phase 的执行
- 用户已给明确 ticket / spec
How to invoke
Clarification needs real user dialogue, so run this stage directly in THIS session — do NOT spawn it, and do NOT improvise: follow these steps so the locked spec is persisted for the execution stages.
- Evaluate the clarification criteria for "$ARGUMENTS":
- Strategic — new feature / milestone / unclear business scope → gstack
/office-hours+/plan-ceo-review - Phase — ≥2 open implementation decisions / unclear cross-phase API contract → GSD
/gsd-discuss-phase - Subtask — ≥2 distinct approaches / core algorithm / API contract design / high error cost → superpowers brainstorming
- Strategic — new feature / milestone / unclear business scope → gstack
- For each layer that fires, hold the dialogue with the user (use AskUserQuestion for option-style decisions) and lock every open decision.
- Transparent-skip layers that don't fire — state which were skipped and why.
- Persist the locked decisions to
.planning/via planning-with-files (findings.md/task_plan.md).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 83 lines · 147 tokens per session scan A 66998f182c3d
discuss-strategic is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 12d ago), licensed Apache-2.0. It adds 147 tokens to every session and 1,084 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
setup
Setup orchestrator for the Octowiz Bridge. Re-runs the live environment check, builds a gap list, and runs only the phases needed: plugins, memory, repo, verify. Invoked automatically by octowiz:octowiz when hard gaps are detected.
octowiz
Octowiz AI coding workflow coordinator. Reads IntegraHub memory doctrine at runtime, detects where you are in the development lifecycle, and routes to the right skill combination from superpowers + mattpocock-skills. Use this skill at the START of any development work — whether you have a fresh idea, an existing plan…
forge
Run a Planner→Dev→Test→Learn workflow for feature development with automatic bug-fix loops and state checkpointing.
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…