Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Show AGNTCY/SLIM/CASA integration status — whether upstream AGNTCY packages are installed, which transport (local vs SLIM) is active, and whether CASA enforcement is enabled. Use when the user asks "is AGNTCY configured?", "show SLIM/CASA status", or "is AGNTCY/IOC integration active?".
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 8% | 0% |
| case-02 | ✗→✓ | ▲ Improved | -47% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -21% | 0% |
| case-05 | ✗→✓ | ▲ Improved | -66% | 0% |
| case-06 | ✗→✓ | ▲ Improved | -54% | 0% |
Scaffolding stub — not yet implemented. This skill will report, once ruflo-agntcy ships real logic (see ADR-380):
@claude-flow/agntcy (TS) and/or the Rust ruflo-agntcy crate are installed as optionalDependencies, or absent (the expected default today — no such upstream package exists yet publicly).allow/deny/budget_usd/expires_at currently in force (ADR-380 §3).hive-mind_broadcast/hive-mind_consensus.agent.identity, coordination.episode, authorization.decision, etc., ADR-380 §5) are being emitted through ruflo-observability.Until upstream AGNTCY/SLIM packages exist, this status check MUST report "not configured — see ADR-380" rather than fabricate a healthy status. No network call to AGNTCY infrastructure (Directory, SLIM broker) is safe to make from this skill until a real client library is available.
Other measured skills in the registry, with their headline benchmark lift.