Skill allowed-tools pre-activates deferred tools

What it does

When a skill loads, the deferred tools named in its allowed-tools list are activated, so the model does not have to search for them first. It starts with giving a skill's frontmatter that key.

Source

ganja-code-mi9 (a skill's allowed-tools list pre-activates deferred tools).

The bead is closed when this issue is published, with its external reference pointing here (#38).

File and line references in this issue are to main as of 75a7a92.

Against the three criteria

• Direction (README): The README's only word on tools is "permission-gated tools" (README.md:6); it says nothing about MCP or deferred loading.
• Today's terminal users: It matters to a user whose MCP tools exceed the deferral threshold (32 by default, crates/ganja-core/src/config.rs:1581).
• Evidence: A follow-up D492's plan named, with no use report since. Deferral::activate exists (crates/ganja-tool/src/deferral.rs:188); a command's frontmatter refuses allowed-tools on purpose because accepting it "would promise something nothing enforces" (crates/ganja-core/src/command.rs:1478-1480).

Depends on

Nothing.

Verdict

• Verdict: do
• Size: S — one commit, no plan.
• Exception to the probe rule: no.
• Date: 2026-09-19
• Verdict ticket: #43

Theme: #55

Start by reading crates/ganja-tool/src/deferral.rs around Deferral::activate, then inspect crates/ganja-core/src/command.rs around the allowed-tools frontmatter handling and crates/ganja-core/src/config.rs:1581 for the deferral threshold. Done means a skill's allowed-tools entries activate matching deferred tools, with the behavior covered by the project's relevant checks.