Borrowing it
Nothing to install: this file belongs to SCStelz/security-investigator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SCStelz/security-investigator/main/.github/skills/mitre-coverage-report/SKILL.mdgit clone --depth 1 https://github.com/SCStelz/security-investigatorWrote 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/scstelz/security-investigator/mitre-coverage-report)<a href="https://agentmods.dev/skills/scstelz/security-investigator/mitre-coverage-report"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/mitre-coverage-report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/scstelz/security-investigator/mitre-coverage-report"><img src="https://agentmods.dev/badge/skills/scstelz/security-investigator/mitre-coverage-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 453 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Data Exfiltration · line 165 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 530 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00115 | $0.09483 |
| Opus 5 | $0.00057 | $0.04741 |
| Sonnet 5 | $0.00023 | $0.01897 |
| Haiku 4.5 | $0.00012 | $0.00948 |
Grade A, and why
mitre-coverage-report scanned grade A with 0 findings 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 10d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 536 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MITRE ATT&CK Coverage Report — Instructions
Purpose
This skill generates a comprehensive MITRE ATT&CK Coverage Report analyzing detection coverage across the ATT&CK Enterprise framework. It inventories all analytic rules and custom detections, maps them to MITRE tactics and techniques, identifies coverage gaps, and provides prioritized recommendations for improving detection posture.
Entity Type: Sentinel workspace (from config.json)
| Scope | Data Sources | Use Case |
|---|---|---|
| Workspace-wide (default) | Analytic Rules (REST), Custom Detections (Graph), SOC Optimization (REST), SecurityAlert/SecurityIncident (KQL) | Full MITRE coverage analysis |
| Operational correlation | SecurityAlert, SecurityIncident | Which MITRE-tagged rules actually produce alerts and incidents |
What this report covers: Tactic-level coverage matrix with per-tactic technique counts and percentages, technique-level drill-down with rule-to-technique mapping, coverage gap identification against the full ATT&CK Enterprise framework, SOC Optimization threat scenario alignment (AiTM, ransomware, BEC, etc.), untagged rule remediation with AI-suggested MITRE tags, ICS/OT technique tracking, operational MITRE correlation (which rules actually fire), and a composite MITRE Coverage Score.
Complementary to: This skill pairs with the sentinel-ingestion-report skill — ingestion report covers data volume, tier optimization, and cost; MITRE coverage report covers detection posture against the ATT&CK framework. Run both for a complete workspace assessment.
Architecture
┌──────────────────────────────────────────────────────────────────┐
│ YAML query files PowerShell script LLM render │
│ queries/phase1-3/ ──→ Invoke-MitreScan.ps1 ──→ Phase 4 │
│ (6 .yaml files) (~1030 lines) (SKILL- │
│ • az rest (Sentinel API) report.md) │
│ • Invoke-MgGraphRequest │
│ • az monitor (KQL) │
│ • mitre-attck-enterprise.json │
│ • m365-platform-coverage.json (CTID) │
│ ↓ │
│ temp/mitre_scratch_<ts>.md │
│ (~35 KB, 18+ sections) │
└──────────────────────────────────────────────────────────────────┘
What ships with it
17 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- Invoke-MitreScan.ps1 151 KB runs code
- known-kql-tables.json 17 KB
- m365-platform-coverage.json 15 KB
- mitre-attck-enterprise.json 32 KB
- queries/phase1/M1-AnalyticRuleMitre.yaml 960 B
- queries/phase1/M2-CustomDetectionMitre.yaml 645 B
- queries/phase2/M3-SocOptCoverage.yaml 1.3 KB
- queries/phase3/M4-AlertFiringByMitre.yaml 1.7 KB
- queries/phase3/M5-IncidentsByTactic.yaml 1.2 KB
- queries/phase3/M6-PlatformAlertCoverage.yaml 1.3 KB
- queries/phase3/M7-TableIngestionVolume.yaml 842 B
- queries/phase3/M8-ConnectorHealth.yaml 1.4 KB
- queries/phase3/M9-TableTierClassification.yaml 1.2 KB
- render_dashboard.py 25 KB runs code
- SKILL-report.md 60 KB
- slice_scratch.py 6.5 KB runs code
- svg-widgets.yaml 19 KB
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.
- 10d ago First seen · 536 lines · 115 tokens per session scan A ff99ebaf45f4
mitre-coverage-report is a skill published in the GitHub repository SCStelz/security-investigator (245 stars, last pushed 2d ago), licensed MIT. It adds 115 tokens to every session and 9,483 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…