Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/unitoneai/securityskills/scanner-tuningnpx skills add UnitOneAI/SecuritySkills --skill scanner-tuninggit clone --depth 1 https://github.com/UnitOneAI/SecuritySkillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/unitoneai/securityskills/scanner-tuning)<a href="https://agentmods.dev/skills/unitoneai/securityskills/scanner-tuning"><img src="https://agentmods.dev/badge/skills/unitoneai/securityskills/scanner-tuning.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00074 | $0.06353 |
| Opus 5 | $0.00037 | $0.03177 |
| Sonnet 5 | $0.00015 | $0.01271 |
| Haiku 4.5 | $0.00007 | $0.00635 |
Grade B, and why
scanner-tuning scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Linux Auth: [SSH key (preferred) | SSH password with sudo | root | N/A] How it starts
The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Scanner Tuning -- CVSS 4.0 / CWE
Frameworks: CVSS 4.0 (FIRST.org), CWE (MITRE) Role: Security Engineer Time: 30-60 min Output: Tuned scan policy configuration, false positive analysis, severity override documentation, and cross-scanner correlation report
When to Use
If a target is provided via arguments, focus the review on: $ARGUMENTS
Use this skill when vulnerability scan results contain excessive false positives, when configuring or reconfiguring scan policies for new environments, when evaluating whether to use authenticated vs unauthenticated scanning, when scanner severity ratings do not align with actual risk, when onboarding a new scanner or comparing results across multiple scanners, or when scan performance (duration, resource consumption) needs optimization.
Do not use when: The task is triaging specific CVEs from scan output (use cve-triage), prioritizing patches from a remediation backlog (use patch-prioritization), or analyzing software composition (use sbom-analysis).
Context the Agent Needs
Before starting, collect or confirm:
- Scanner platform(s): Which scanner(s) are in use? (Qualys VMDR, Tenable Nessus/IO/SC, Rapid7 InsightVM/Nexpose, OpenVAS/Greenbone, Snyk, Trivy, Grype, Nuclei)
- Current scan policies: Existing scan policy names, configurations, and plugin/check selections
- Scan scope: Target IP ranges, hostnames, applications, containers, or cloud accounts
- Authentication status: Are scans currently authenticated (credentialed) or unauthenticated?
- False positive examples: Specific findings suspected or confirmed as false positives, with evidence
- Scan frequency: Current scan schedule and any performance constraints
- Result volume: Approximate number of findings per scan cycle and false positive rate if known
- Compliance requirements: Whether scans must meet specific compliance mandates (PCI ASV, DISA STIG, CIS Benchmark)
- Multi-scanner context: If using multiple scanners, which ones and how results are currently correlated
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 442 lines · 74 tokens per session scan B 389d96d78413
scanner-tuning is a skill published in the GitHub repository UnitOneAI/SecuritySkills (59 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 6,353 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
cis-aws-foundations-2.1.3
Ensure Organizations management account is not used for workloads.
cis-aws-foundations-2.12
Ensure access keys are rotated every 90 days or less.
cis-aws-foundations-4.1
Ensure CloudTrail is enabled in all regions.
cis-aws-foundations-4.4
Ensure that server access logging is enabled on the CloudTrail S3 bucket.
cis-aws-foundations-6.1.2
Ensure CIFS access is restricted to trusted networks to prevent unauthorized access.
cis-aws-foundations-2.5
Ensure MFA is enabled for the 'root' user account.