Skip to content
Back to skills

Agents

ASecurity

PLAN-020 Phase 0 item 5 governance probe — verifies that `check_agent_spawn.py` BLOCKS dispatch via the native subagent rail when the spawn prompt has no skill content (neither `## SKILL CONTENT` inline NOR `## SKILL REFERENCE`). Expected hook output for any Task tool call dispatching this agent: `{"decision":"block","reason":"GOVERNANCE: missing_skill_content: ..."}`. If the hook ALLOWS this dispatch, native rail has a governance gap and Phase 1 is NO-GO.

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 2, 2026
ai-agentsgo

Security analysis

A100/100

Pro scans all 14 files and shows the line behind each finding

Scanned September 2, 2026

npx -y skills add Canhada-Labs/ceo-orchestration --skill agents --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Agents?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Agents
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/canhada-labs-agents/badge)](https://www.skillsdirectory.com/skills/canhada-labs-agents)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: _probe_missing_skill
description: PLAN-020 Phase 0 item 5 governance probe — verifies that `check_agent_spawn.py` BLOCKS dispatch via the native subagent rail when the spawn prompt has no skill content (neither `## SKILL CONTENT` inline NOR `## SKILL REFERENCE`). Expected hook output for any Task tool call dispatching this agent: `{"decision":"block","reason":"GOVERNANCE: missing_skill_content: ..."}`. If the hook ALLOWS this dispatch, native rail has a governance gap and Phase 1 is NO-GO.
version: anthropic-subagent-v1
tools: []
---

# _probe_missing_skill

This file exists ONLY to test that the framework's `check_agent_spawn.py`
hook correctly rejects native-rail spawns that lack skill content. It is
not a real agent and should never be invoked outside the Phase 0 native-
probe harness.

## Probe expectation

When the CEO (or any caller) issues a Task tool call referencing this
agent, the PreToolUse hook `check_agent_spawn.py` must emit:

```json
{"decision":"block","reason":"GOVERNANCE: <reason_code>: <detail>"}
```

The exact reason code may be `missing_skill_content` (inline path) or
`reference_missing` (reference path) — both are acceptable.

If the hook emits `{"decision":"allow"}`, the probe FAILS and Phase 1
is NO-GO per PLAN-020 §4 Phase 0 item 5.

## Why this matters

PLAN-019 P1-SEC-B hardened the inline `## SKILL CONTENT` 256-byte floor
+ fence/comment mask in `_has_skill_content`. PLAN-020 expands the
sentinel surface (Phase 2 adds `## SKILL REFERENCE` parallel path).
Native-rail dispatch must inherit equivalent or stricter discipline,
not bypass.

## Cleanup

This file is deleted in the Phase 0 closeout commit OR after Phase 1
recognition lands and the probe is moved into the test suite as a
`subprocess` harness invocation. It MUST NOT remain in main long-term.

Files in this skill

  • _dispatch.md2.5 KB
  • _probe_architect.md1.9 KB
  • _probe_canonical_edit.md1.8 KB
  • _probe_missing_skill.md1.8 KB
  • code-reviewer.md6.6 KB
  • devops.md4.3 KB
  • identity-trust-architect.md11.4 KB
  • incident-commander.md14.1 KB
  • llm-finops-architect.md13 KB
  • performance-engineer.md6.1 KB
  • qa-architect.md7.1 KB
  • security-engineer.md8.5 KB
  • threat-detection-engineer.md11.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.