anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 18:25:32 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

feat: Support disable-model-invocation field in skill frontmatter #8434

New Issue
Open
opened 2026-02-16 18:09:58 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 18:09:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @rian-dolphin on GitHub (Feb 3, 2026).

Originally assigned to: @thdxr on GitHub.

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Claude Code supports a disable-model-invocation: true frontmatter field in SKILL.md files that prevents skills from being loaded into the model's context while still allowing users to invoke them via slash commands.

Currently, OpenCode appears to ignore this field. Skills with disable-model-invocation: true are still visible to the model.

Steps to reproduce:

  1. Create a skill with disable-model-invocation: true in the frontmatter
  2. Start a new OpenCode chat
  3. Ask the model what skills it has access to
  4. Observe that the skill appears in the list, even though it shouldn't be visible to the model

Use case

When working with many skills (either project-specific or in a global user config), loading all skill names and descriptions into every chat consumes context unnecessarily. Some skills are better suited for direct user invocation rather than model discovery—for example, utility scripts or workflows that the user knows when to trigger.

Supporting disable-model-invocation would allow users to retain access to these skills via /skill-name while keeping the model's context cleaner.

Note on scope

I understand this is a Claude Code-specific feature, and OpenCode isn't aiming for full feature parity. If this falls outside the project's goals, that's completely understandable—just wanted to surface the use case in case it aligns with the direction you're heading.

Originally created by @rian-dolphin on GitHub (Feb 3, 2026). Originally assigned to: @thdxr on GitHub. ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request Claude Code supports a `disable-model-invocation: true` frontmatter field in SKILL.md files that prevents skills from being loaded into the model's context while still allowing users to invoke them via slash commands. Currently, OpenCode appears to ignore this field. Skills with `disable-model-invocation: true` are still visible to the model. **Steps to reproduce:** 1. Create a skill with `disable-model-invocation: true` in the frontmatter 2. Start a new OpenCode chat 3. Ask the model what skills it has access to 4. Observe that the skill appears in the list, even though it shouldn't be visible to the model ### Use case When working with many skills (either project-specific or in a global user config), loading all skill names and descriptions into every chat consumes context unnecessarily. Some skills are better suited for direct user invocation rather than model discovery—for example, utility scripts or workflows that the user knows when to trigger. Supporting `disable-model-invocation` would allow users to retain access to these skills via `/skill-name` while keeping the model's context cleaner. ### Note on scope I understand this is a Claude Code-specific feature, and OpenCode isn't aiming for full feature parity. If this falls outside the project's goals, that's completely understandable—just wanted to surface the use case in case it aligns with the direction you're heading.
yindo commented 2026-02-16 18:09:58 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Feb 3, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #11122: Hidden agents/commands/plugins/Claude Code-style skills ought not be discoverable - relates to controlling skill visibility to the model

Feel free to ignore if this doesn't address your specific case.

@github-actions[bot] commented on GitHub (Feb 3, 2026): This issue might be a duplicate of existing issues. Please check: - #11122: Hidden agents/commands/plugins/Claude Code-style skills ought not be discoverable - relates to controlling skill visibility to the model Feel free to ignore if this doesn't address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#8434
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?