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 skills/easyinplay/harnessed/multispecnpx skills add easyinplay/harnessed --skill multispecgit clone --depth 1 https://github.com/easyinplay/harnessedWhat 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.00179 | $0.01963 |
| Opus 5 | $0.00089 | $0.00981 |
| Sonnet 5 | $0.00036 | $0.00393 |
| Haiku 4.5 | $0.00018 | $0.00196 |
Grade A, and why
verify-multispec 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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
verify-multispec workflow (v3)
Overview
2-phase sub-workflow mapping CLAUDE.md "Verify 阶段 — 关键发布 / 大重构 PR 升级 Agent Team Pattern C" onto harnessed runtime (Phase v3.0-3.4 W0.13e — D-04 Stage ④ Verify 7 sub + D-11 Agent Teams + Pattern A sub-workflow ship)。
| phase | id | upstream | model | capability | gate / on |
|---|---|---|---|---|---|
| 1 | 01-team-create |
claude-platform | opus | {{ capabilities.agent-teams-create.cmd }} |
parallelism: agent-teams-upgrade.fires; on: is_major_release OR is_large_refactor → invoke |
| 2 | 02-team-cleanup |
claude-platform | haiku | {{ capabilities.agent-teams-shutdown.cmd }} |
mandatory 防呆清单 |
Per-phase config loads from workflows/verify/multispec/workflow.yaml; phase 01 spawns 4
background teammate (code-review + gstack-review + gstack-cso + gstack-qa) with
Agent(name, run_in_background=true) — the team forms implicitly on the FIRST spawn (CC
2.1.178+ has no create step / no create tool), teammates 互相 SendMessage 质询 findings 是否
真问题 (NOT fire-and-forget); phase 02 mandatory 按名请求每个 teammate shut down (bundled
Agent Teams cleanup discipline — 团目录在 session 退出时自动清理,无独立 teardown 工具,
剩下的纪律是别把 teammate 落在运行态)。
Capability refs
Sister workflows/capabilities.yaml entries:
agent-teams-create— Bucket 5 Agent Teams (impl: claude-platform, cmd:Agent(name, run_in_background=true))agent-teams-send-message— Bucket 5 Agent Teams (impl: claude-platform, cmd: SendMessage)agent-teams-shutdown— Bucket 5 Agent Teams (impl: claude-platform, cmd:ask the <teammate-name> teammate to shut down)code-review— Bucket 1 mattpocock (teammate 1)gstack-review— Bucket 3 治理关卡 (teammate 2 Paranoid Staff Engineer)gstack-cso— Bucket 3 治理关卡 (teammate 3 安全审查)gstack-qa— Bucket 3 治理关卡 (teammate 4 端到端 QA)
Parallelism + on gate refs
Sister workflows/judgments/parallelism-gate.yaml:
agent-teams-upgrade.fires— 5 OR-chain (teammate_send_message_needed / subagent_context_overflow / shared_task_list / opposing_hypothesis_debate / fullstack_three_way)
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.
- 2d ago First seen · 103 lines · 179 tokens per session scan A 847635b33b3b
verify-multispec is a skill published in the GitHub repository easyinplay/harnessed (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 179 tokens to every session and 1,963 once invoked, about $0.0009 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
security-ownership-map
Analyze git repositories to build a security ownership topology (people-to-file), compute bus factor and sensitive-code ownership, and export CSV/JSON for graph databases and visualization. Trigger only when the user explicitly wants a security-oriented ownership or bus-factor analysis grounded in git history (for…
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
comet-native
Comet Native 工作流。当用户明确调用 /comet-native、要求启动或恢复 Native change，或入口路由到 Native 时使用。.
comet-hotfix
Comet 预设 —— 通过 open-build-verify-archive 短流程修复已有行为 bug。.
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
comet-design
Comet Classic 阶段 2 —— 为 change 产出深度技术 Design Doc。.