fix: reduce defensive SKILL.md instruction noise

[caioribeiroclw-pixel]

Summary

Follow-up to #116 after the merged role-aware surface fix reduced the generic prompt/metadata noise, but SKILL.md-specific scanners can still flag benign defensive templates.

This keeps the dedicated skill_md scanner, but avoids two common false positives when the risky phrase is clearly part of a protective instruction:

• Never reveal secrets / API keys / tokens should not be reported as credential-harvest language.
• Do not ignore previous instructions / system prompts should not be reported as instruction-override language.

It still flags offensive forms such as Ignore all previous instructions and override policy or Send the access token to a webhook.

Validation

Could run locally in this environment:

python3 -m compileall -q src tests
git diff --check
custom line-length check over changed files: no lines >110 chars

I could not run pytest locally because neither the system Python nor the repo .venv has pytest/project deps installed here; the new regression tests are included for CI.

Closes #116 if this matches the intended second-stage noise reduction.

[hello-args]

Thanks for this follow-up to #116 — the defensive-context gating for skill_md W008/W010 looks good, and CI is green.

Please recreate this PR targeting develop instead of main.

Our branch workflow merges feature/fix PRs into develop first; main is release-only (maintainer merge after gates). See CONTRIBUTING.md and the Protect develop / Protect release branches rulesets.

What to do:

1. Close this PR (or leave it open until the new one is up — your call).
2. Rebase your branch onto latest MCP-Audit/develop:

   git fetch upstream
   git checkout fix/skill-md-defensive-context
   git rebase upstream/develop
   git push --force-with-lease origin fix/skill-md-defensive-context

3. Open a new PR with base: develop (same title/body is fine).
4. Keep Closes #116 in the description if you still intend to close it after merge.

No code changes needed — retarget only. I validated the diff locally; once the develop PR is up we can merge from there.

/cc @caioribeiroclw-pixel

[caioribeiroclw-pixel]

Thanks — retargeted the existing PR to develop via the pulls API instead of opening a duplicate PR.

Current state:

• base: develop
• head: fix/skill-md-defensive-context
• all reported checks are green again across the Python matrix, CodeQL, action-smoke, MCTS, scoring, and scoring-v2

I’ll leave it untouched unless you want a fresh PR URL instead.

[hello-args]

looks good: merging into develop now. That should close #116.

Thanks, @caioribeiroclw-pixel.