Retired — its runtime-neutrality contract moved to docs/contracts/runtime-neutrality.md. Triggers: none — not routable.
Scanned 9/2/2026
Install to Claude Code
npx -y skills add boshu2/agentops --skill shared --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Shared?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/boshu2-shared-agentops)More formats (shields.io, HTML) on the badges page.
---
name: shared
description: 'Retired — its runtime-neutrality contract moved to docs/contracts/runtime-neutrality.md. Triggers: none — not routable.'
practices: [design-by-contract]
hexagonal_role: domain
consumes: []
produces: []
context_rel: []
skill_api_version: 1
user-invocable: false
metadata:
tier: library
dependencies: []
capabilities: []
effects: []
canonical_status: canonical
disposition: keep_off_path
internal: true
output_contract: none — retired; see docs/contracts/runtime-neutrality.md
---
# Shared — retired
Semantically retired 2026-07-29 (bead `age-skill-overhaul-reboot-sjv7v.11`).
The runtime-neutrality contract this library carried now lives at its
declared owner: [docs/contracts/runtime-neutrality.md](../../docs/contracts/runtime-neutrality.md).
This skill bundles nothing, produces nothing, grants nothing, and is loaded
by nothing. The directory remains only for the observed-zero window: physical
deletion follows once a declared observation period shows no remaining
references resolve here.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...