Built In Agent Feature Gating
Gate built-in agents based on feature flags and entrypoint types so SDK sessions stay lean.
Install
$ agentstack add skill-ychampion-cskill-agents-built-in-agent-feature-gating ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ychampion-cskill-agents-built-in-agent-feature-gating) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
SKILL: Built-In Agent Feature Gating
Domain: agent-management Trigger: Use whenever agent registration should respect CLI entrypoints, SDK toggles, or feature flags before exposing the built-in catalog. Source Pattern: Distilled from reviewed built-in agent registration and feature-flagged runtime catalog implementations.
Core Method
Check entrypoint type, environment toggles, and feature flags before adding each built-in agent to the visible registry. Different entrypoints often need different built-in surfaces: a CLI may want planning or guidance agents, while an SDK or embedded runtime may want a minimal default set. Treat special orchestration modes as their own catalog variant rather than layering them on top of the normal list. This keeps built-in agents discoverable where they belong without leaking extra helpers into every runtime surface.
Key Rules
- Support an explicit “disable built-ins” toggle for SDK or embedded contexts that should expose a minimal surface.
- Treat coordination or orchestration modes as a separate built-in catalog rather than mixing them into the default list.
- Gate specialized built-ins behind feature flags or experiments instead of making them permanently visible.
- Keep the gating logic centralized so every entrypoint evaluates the same rules consistently.
Example Application
Before populating the agent registry, apply these checks so an SDK session can expose no built-ins, a CLI can expose planning or guidance agents when enabled, and a coordinator runtime can swap in its own worker-oriented catalog.
Anti-Patterns (What NOT to do)
- Don’t register all built-in agents unconditionally; ignoring entrypoints or env vars breaks SDK/CLI separation.
- Avoid hardcoding agent lists per mode; fold them into feature flags and helper functions to stay configurable.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ychampion
- Source: ychampion/cskill-agents
- License: MIT
- Homepage: https://x.com/YashasGunderia/status/2039990540016693692?s=20
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.