Skip to content

fix(skills_guard): agent-created dangerous skills ask instead of block#2446

Merged
teknium1 merged 1 commit intomainfrom
hermes/hermes-40b195db
Mar 22, 2026
Merged

fix(skills_guard): agent-created dangerous skills ask instead of block#2446
teknium1 merged 1 commit intomainfrom
hermes/hermes-40b195db

Conversation

@teknium1
Copy link
Copy Markdown
Contributor

Salvage of PR #2271 by @redhelix — skills_guard change only (Mission Control adapter excluded as unrelated).

Agent-created skills with critical security findings were silently blocked. Now they're allowed with a warning logged, since the agent created the skill and blocking it entirely is too aggressive.

Trust Level Verdict Before After
agent-created dangerous Blocked Allowed (warning logged)
agent-created dangerous + force Allowed Allowed
  • Policy table: blockask for agent-created dangerous
  • should_allow_install() returns None for ask (tri-state: True/None/False)
  • format_scan_report() shows NEEDS CONFIRMATION for ask
  • skill_manager_tool.py caller handles None — allows with warning

3 files, +26/-8. 53 skills_guard tests pass.

Changes the policy for agent-created skills with critical security
findings from 'block' (silently rejected) to 'ask' (allowed with
warning logged). The agent created the skill, so blocking it entirely
is too aggressive — let it through but log the findings.

- Policy: agent-created dangerous changed from block to ask
- should_allow_install returns None for 'ask' (vs True/False)
- format_scan_report shows 'NEEDS CONFIRMATION' for ask
- skill_manager_tool.py caller handles None (allows with warning)
- force=True still overrides as before

Based on PR #2271 by redhelix (closed — 3200 lines of unrelated
Mission Control code excluded).
@teknium1 teknium1 merged commit 5c8d7d5 into main Mar 22, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

1 participant