Additive Agent Tool Surface Construction
Merge agent-specific tool sets (MCP clients + fetched tools) into the parent context without disrupting the parent’s existing pool.
Install
$ agentstack add skill-ychampion-cskill-agents-additive-agent-tool-surface-construction ✓ 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-additive-agent-tool-surface-construction) 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: Additive Agent Tool Surface Construction
Domain: tool-surface Trigger: Use this when bringing tools from newly connected MCP servers into the agent’s tool pool while preserving the parent context. Source Pattern: Distilled from reviewed subagent orchestration, isolation, and lifecycle implementations.
Core Method
When a child agent connects extra integrations, treat those capabilities as additions layered over the parent surface rather than as a replacement. Keep the parent client handles intact, append the agent-owned clients, and merge the newly discovered tool definitions alongside the inherited tool pool. Pass the merged clients, merged tools, and the child-owned cleanup handle downstream as one package so later stages can use the expanded surface without mutating the parent session.
Key Rules
- Always start with parent clients and append agent clients in order to avoid losing existing handles that the session still needs.
- Maintain agent tools separately so the agent can union them with the parent’s command/skill catalog without overwriting it.
- Return both the merged clients and tools along with the cleanup closure so callers can pass them downstream transparently.
- Log the before/after counts to aid debugging when tools disappear unexpectedly.
Example Application
When a sub-agent launches with extra MCP servers, use this pattern so it keeps the parent integrations it inherited while also gaining the newly connected agent-specific tools.
Anti-Patterns (What NOT to do)
- Don’t replace the parent client list with just the agent’s clients; that loses the original MCP endpoints.
- Don’t forget to pass the merged tools through the helper that runs the forked agent, or the new MCP servers will appear to succeed but never expose their tools.
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.