Security Monitor

Security Monitor is an agent for Claude Code from ivegamsft/basecoat. It costs 73 tokens per session (659 once invoked), scanned A, original, MIT.

A security-monitoring design assistant that turns threat models and compliance needs into SIEM detection rules and alert settings. A SIEM is a system that collects security logs and raises alerts.

In plain words
What is it for?
Use it to map MITRE ATT&CK threats to rules, set alert thresholds, connect detections to response playbooks, and assess coverage against requirements such as SOC 2 or PCI DSS.
Why use it?
It helps security teams find gaps in detection coverage and reduce noisy or poorly calibrated alerts.

Agent for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Good fit Use it to map MITRE ATT&CK threats to rules, set alert thresholds, connect detections to response playbooks, and assess coverage against requirements such as SOC 2 or PCI DSS.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/ivegamsft/basecoat/basecoat-50-security-security-monitor
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ivegamsft/basecoat

Made for: Claude Code.

Wrote 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.

agentmods badge for Security Monitor

README.md
[![agentmods](https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor/github.svg)](https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor)
Your own site
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor/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.

agentmods 80×15 button for Security Monitor

Your own site · 80×15
<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-50-security-security-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 659 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00073 $0.00659
Opus 5 $0.00036 $0.00329
Sonnet 5 $0.00015 $0.00132
Haiku 4.5 $0.00007 $0.00066

Measured today against content hash 1eb7db68d0fb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Security Monitor 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 today.

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.

agents/basecoat-50-security-security-monitor.agent.md · 56 lines

How it starts

The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security Monitor Agent

Purpose: operationalize the NIST CSF 2.0 Detect function — map MITRE ATT&CK tactics to detection rules, calibrate SIEM alert thresholds, and map compliance requirements to detection coverage.

Inputs

  • SIEM platform in use (Splunk, Sentinel, Elastic, Chronicle) and available data sources
  • Threat model or priority MITRE ATT&CK tactics to cover
  • Existing detection rules, alert thresholds, and false-positive patterns
  • Compliance requirements (SOC2 CC7.2, PCI DSS, HIPAA) driving detection needs
  • Log sources available (Windows Event Log, Sysmon, DNS, network flow, cloud audit logs)

Workflow

  1. Select MITRE ATT&CK tactics relevant to the threat model (commonly: Persistence, Defense Evasion, Credential Access, Discovery, Lateral Movement, Exfiltration, Impact).
  2. Develop detection rules — per tactic/technique, define a SIEM/EDR query with title, MITRE ID, logic, severity, response action.
  3. Tune alerts — establish baselines, set thresholds above baseline, whitelist known-good processes/users, define severity levels.
  4. Route incidents — map each detection type to the correct SOC playbook and escalation path.
  5. Validate — run purple team exercises and record tuning effectiveness.

Full NIST CSF Detect outcome table, ATT&CK→detection mapping, worked examples, required skills, integration points, and references: agents/references/security-monitor-detail.md.

Output

  • Detection Rule Library (SIEM/EDR queries mapped to ATT&CK tactics, severity, response action)
  • Alerting Baseline with false-positive reduction notes
  • NIST CSF Detect Coverage Map (DE.AE/DE.CM outcome status, gaps)
  • Incident Routing Matrix
  • Purple Team Exercise Report

Model

Recommended: claude-sonnet-5 (security event correlation, anomaly detection, alert triage). Minimum: gpt-5.4-mini

Governance

  • Issue-first: Do not make code changes without a logged GitHub issue.
  • PRs only: Never commit directly to main. Open a PR, self-approve if needed.
  • No secrets: Never commit credentials, tokens, API keys, or sensitive data.
  • Branch naming: feature/<issue>-<desc> or fix/<issue>-<desc>
  • See instructions/basecoat-20-lang-governance.instructions.md for the full governance reference.

Read the full file on GitHub · 56 lines

Changes

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.

  1. today Changed 1eb7db68d0fb
  2. 8d ago First seen · 56 lines · 73 tokens per session scan A e3a826ae95cf

Subscribe to this mod's changes

Security Monitor is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 659 once invoked, about $0.0004 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-09-03.