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 multispecgit 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/multispec)<a href="https://agentmods.dev/skills/easyinplay/harnessed/multispec"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/multispec/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/easyinplay/harnessed/multispec"><img src="https://agentmods.dev/badge/skills/easyinplay/harnessed/multispec.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.00196 | $0.01947 |
| Opus 5.5 | $0.00078 | $0.00779 |
| Sonnet 5.5 | $0.00039 | $0.00389 |
| Haiku 4.5 | $0.00020 | $0.00195 |
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 25d 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 — 99 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 升级 {{ host.team.singular }} Pattern C" onto harnessed runtime (Phase v3.0-3.4 W0.13e — D-04 Stage ④ Verify 7 sub + D-11 {{ host.team.attributive }} + 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 {{ host.teammate }} (code-review + gstack-review + gstack-cso + gstack-qa) with
{{ host.multispec_spawn_note }}; phase 02 mandatory {{ host.teams_cleanup_note.shutdown_phrase }} (bundled
{{ host.teams_cleanup_note.multispec }}
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 ({{ host.teammate }} 1)gstack-review— Bucket 3 治理关卡 ({{ host.teammate }} 2 Paranoid Staff Engineer)gstack-cso— Bucket 3 治理关卡 ({{ host.teammate }} 3 安全审查)gstack-qa— Bucket 3 治理关卡 ({{ host.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)
Phase-level on clause (critical-release 升级触发):
if: phase.is_major_release == true or phase.is_large_refactor == true→action: invoke- else →
action: skip
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.
- 25d ago Changed · -4 lines · +17 tokens per session b8c1dae112dc
- 1mo 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 3d ago), licensed Apache-2.0. It adds 196 tokens to every session and 1,947 once invoked, about $0.0008 per session on Opus 5.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
codex-ab
Run an A/B codex review experiment — holistic codex review vs 3 focused dimension passes (security, ecto, liveview) on the branch diff, classify findings, report a panel-value verdict. Use when the branch is fresh, before any codex review runs.
pre-pr-audit
Pre-PR confidence audit with 5-dimension scoring. Use when: final check before commit/push/PR, evaluating PR readiness, assessing test quality + risk + coverage holistically. Triggers: pre-pr, readiness check, confidence audit, final verification, ready to PR, how confident. Not for: code review (use…
codex-loop
Fix Elixir/Phoenix code until Codex CLI review comes back clean — bounded review, fix, verify loop before opening a PR. Use when codex is installed and you want an external cross-model critic on your changes before pushing.
spike-consumer-adversarial
OI-3 spike harness — heavy consumer, ADVERSARIAL arm. Worst-case early-exit test: the mid-workflow Skill call has no continuation guardrail and the guidance skill ends with a final-sounding anchor. Use only when explicitly invoked by the spike harness with a TRIALID and data path.
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.
code-standards
Apply a disciplined engineering workflow to any code change. Use whenever implementing a feature, fixing a bug, or refactoring — before writing code, not after. Walks orient → baseline → smallest change → test → verify → self-review, and enforces language-agnostic hard gates (don't mass-reformat, keep the linter and…