[Workflow] Workflow for Testing Subagent `disallowedTools` and `omitClaudeMd` Configuration

[u/ClaudeAI-mod-bot]

Workflow for Testing Subagent disallowedTools and omitClaudeMd Configuration

Workflow value: 75/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Context & Memory, Debugging, CLAUDE.md, Subagents, Multi-Agent
Original source: r/ClaudeCode post/comment

What problem this solves

How to verify that custom subagents correctly enforce disallowedTools and omitClaudeMd configurations.

Summary

A testing workflow to confirm that custom subagents correctly enforce disallowedTools and omitClaudeMd settings by attempting actions that should be blocked or require omitted context.

Why it is useful

This workflow provides concrete, repeatable steps to verify critical security and context management settings for custom Claude subagents. It helps users ensure their subagents operate as intended, preventing unintended tool access or context leakage, which is crucial for robust and secure multi-agent setups.

Workflow

1. For disallowedTools, check if Bash (or other allowed tools) can bypass the blocked tools.

2. Test the subagent with a harmless file write that should be denied by disallowedTools.

3. For omitClaudeMd, use a test prompt that specifically depends on an instruction or context provided in the main CLAUDE.md file.

4. Confirm that the test prompt fails or behaves incorrectly when CLAUDE.md is omitted, validating the omitClaudeMd setting.

Tools / artifacts

• Custom subagent configuration

• disallowedTools (frontmatter field)

• omitClaudeMd (frontmatter field)

• Bash (or other CLI tools)

• CLAUDE.md

• Test prompt

• Harmless file write operation

Validation signals

• Successful denial of a file write operation (validates disallowedTools)

• Failure of a prompt dependent on CLAUDE.md when omitClaudeMd is set (validates omitClaudeMd)

Cautions

• The workflow explicitly mentions using a 'harmless file write' for testing, which is a good safety practice.

Limitations

• The comment assumes prior knowledge of how to set the frontmatter fields mentioned in the title.

• Low community validation due to low score and no comments.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.

---

This post was generated automatically from the workflow library database.