You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scan policies control all tuning knobs, detection thresholds, and rule enablement in Skill Scanner. Every setting has a sensible default; custom policies merge on top so you only specify what you want to change.
Good balance of detection and false-positive rate. Broad benign allowlists, demotion in docs, known installer domains trusted.
strict
Lowest thresholds, most sensitive. Scans all files (no inert extension skip), no known installer demotions, narrow allowlists. Best for untrusted/external skills and compliance audits.
permissive
Highest thresholds, fewer findings, broader whitelists. Best for trusted internal skills or high-FP workflows.
When a pipeline reads a matching file, the taint is upgraded to SENSITIVE_DATA.
Field
Type
Default
Affects
patterns
list[regex]
/etc/passwd, ~/.ssh, .env, .pem, etc.
Pipeline taint upgrade to SENSITIVE_DATA
llm_analysis — LLM context budget thresholds
Controls LLM context budget thresholds for LLM and meta analyzers. Content within budget is sent in full; content exceeding the budget is skipped entirely and an LLM_CONTEXT_BUDGET_EXCEEDED INFO finding is emitted.
Field
Type
Default
Affects
max_instruction_body_chars
int
20000
Maximum character length for a single instruction body sent to the LLM
max_code_file_chars
int
15000
Maximum character length for a single code file sent to the LLM
max_referenced_file_chars
int
10000
Maximum character length for a single referenced file sent to the LLM
max_total_prompt_chars
int
100000
Maximum total characters across the entire LLM prompt
max_output_tokens
int
8192
Maximum output tokens for LLM responses (both LLM analyzer and meta-analyzer)
meta_budget_multiplier
float
3.0
Multiplier applied to all input limits above for the meta analyzer (e.g. 3x = 60K instruction, 45K/file, 300K total)
analyzers — Enable or disable built-in analysis passes
Field
Type
Default
Affects
static
bool
true
Enable/disable YAML+YARA pattern analyzer
bytecode
bool
true
Enable/disable .pyc bytecode analyzer
pipeline
bool
true
Enable/disable shell pipeline taint analyzer
finding_output — Output normalization, dedupe behavior, and traceability metadata
Field
Type
Default
Affects
dedupe_exact_findings
bool
true
Removes exact duplicates from overlapping analyzers
dedupe_same_issue_per_location
bool
true
Collapses same issue at same file/line/snippet/category across analyzers
same_issue_preferred_analyzers
list[str]
["meta_analyzer", "llm_analyzer", ...]
Chooses which analyzer's details survive same-issue collapse
same_issue_collapse_within_analyzer
bool
true
If true, also collapses same-issue findings from one analyzer
annotate_same_path_rule_cooccurrence
bool
true
Adds same_path_other_rule_ids metadata for findings on the same path
attach_policy_fingerprint
bool
true
Adds policy name/version/fingerprint metadata to each finding
severity_overrides — Raise or lower any rule's severity
Field
Type
Default
Affects
severity_overrides
list[{rule_id, severity, reason}]
[]
Override finding severity per rule
severity_overrides:
- rule_id: BINARY_FILE_DETECTEDseverity: MEDIUMreason: "Our policy treats unknown binaries as medium risk"
disabled_rules — Completely suppress specific rule IDs