Monitor CI
nrwl/nx
Monitor Nx Cloud CI pipeline and handle self-healing fixes. An agent skill from nrwl/nx.
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on…
Install Detection And Monitoring
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cbrock84/headcount detection-and-monitoring --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .claude/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .claude/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoringType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cbrock84/headcount detection-and-monitoring --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .agents/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .agents/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cbrock84/headcount detection-and-monitoring --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .cursor/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .cursor/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cbrock84/headcount.git --path plugins/security/skills/detection-and-monitoring--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cbrock84/headcount detection-and-monitoring --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .gemini/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .gemini/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cbrock84/headcount detection-and-monitoringInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .github/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .github/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cbrock84/headcount --skill detection-and-monitoring -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cbrock84/headcount detection-and-monitoring --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cbrock84/headcount.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/security/skills/detection-and-monitoring .opencode/skills/detection-and-monitoring && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "detection-and-monitoring" agent skill from https://github.com/cbrock84/headcount/tree/main/plugins/security/skills/detection-and-monitoring into .opencode/skills/detection-and-monitoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "detection-and-monitoring", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
detection-and-monitoring- GitHub stars
- 2k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 709 words
- Files
- 2 (incl. references)
- Skills in repo
- 178
- Repo updated
- First seen
- Licence
- MIT
At a glance
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on…
- DevOps & Cloud work in your project
- SKILL.md covers Decide what to log by asking…, Centralize, and make the copy…, Write detections for behavior,… and Tune ruthlessly, because alert…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Detection And Monitoring is an agent skill from cbrock84/headcount. Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/sources.md`).
It sits in DevOps & Cloud. The repository describes itself as: An agent organization structured as a company — 15+ departments, 125+ skills, each independently installable, citing the standards and regulators that settle the question. Runs… The licence is MIT.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “Use the detection-and-monitoring skill to build the capability to notice an attack in progress — deciding what to log and retain, centralizing it…”
- “/detection-and-monitoring”
What it can do on your machine
Read from SKILL.md and the folder at commit 98d1c17. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Detection And Monitoring loads about 1.3k tokens when it runs, and up to ~1.8k if it reads all its reference files. Until then it costs about 132 tokens; SKILL.md has 709 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from cbrock84/headcount at commit 98d1c17, republished under its MIT licence (© cbrock84). 709 words, ~1,273 tokens.
Download SKILL.mdSave it as
.claude/skills/detection-and-monitoring/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- detection-and-monitoring
- description
- Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires. Use this to design or assess monitoring coverage, work out why an incident went unnoticed, cut alert volume without losing signal, or decide what a detection capability should cost.
Detection and monitoring
Incident response assumes someone noticed. Most organizations that respond well to incidents found out from a customer, a vendor, or an extortion note, and the gap between compromise and discovery is where nearly all of the damage accumulates.
Decide what to log by asking what you would need afterward
Work backwards from the questions an investigation asks: who authenticated, from where, and what did they then do. That points at a short list that matters far more than volume.
- Identity events — authentication success and failure, MFA changes, privilege grants, new API keys and tokens, consent grants to applications.
- Endpoint process activity — what ran, what spawned it, what it connected to.
- Administrative actions in the platforms that hold your data, especially permission and sharing changes.
- Network egress where you have it, and DNS, which is cheap and unusually informative.
Retention decides whether you can investigate at all. Intrusions are commonly discovered months after entry, so logs kept for thirty days answer none of the useful questions. Split it: a short hot window you can search fast, and a longer cold archive you can still reach.
Centralize, and make the copy hard to erase
Logs stored only on the system that produced them are logs the attacker controls. Ship them off the host as they are written, to a destination with different credentials from the systems it collects from — otherwise one compromised administrator account ends both the intrusion and the evidence of it.
Write detections for behavior, not for events
A single event is almost never an incident. What distinguishes an attacker is a sequence: authentication from a new location, followed by a mailbox rule creation, followed by a bulk download.
- Start from the techniques that actually apply to you. Coverage is a property of your own estate, not of a vendor's rule count.
- Detect the steps an attacker cannot skip — persistence, privilege escalation, credential access, and exfiltration — rather than the tools they might use, which change.
- High-signal detections available cheaply: inbox rules that forward or delete externally, new federation or identity-provider trust, disabled logging, impossible travel on administrative accounts, and mass file access by a single principal.
Every detection needs a documented response. A detection that fires with no defined next step becomes noise on its second occurrence.
Tune ruthlessly, because alert fatigue is the real failure mode
An alert that is wrong most of the time trains people to close it without reading. The team stops noticing, and the eventual real one closes the same way.
Measure the proportion of alerts that are actually actioned. Anything consistently below roughly half is a tuning problem, and the fix is narrowing or suppressing the rule rather than adding another analyst. A smaller number of trustworthy detections beats broad coverage nobody believes.
Show full SKILL.md (247 more words)Show less
Decide who is watching, and when
Coverage hours are an explicit decision with a cost. Business-hours monitoring means an intrusion starting on Friday evening runs unobserved for two days, which is exactly why attacks are timed that way. If you cannot staff around the clock, say so, and choose a small number of detections that page a human at any hour rather than pretending the queue is monitored.
Outsourcing detection is legitimate and does not outsource the decision. The provider escalates; someone inside still has to be reachable and authorized to disconnect something.
Test that it would actually fire
Detection coverage is assumed far more often than it is verified. Run the behavior — a benign version of the technique — and confirm the alert arrives, reaches a person, and carries enough context to act on. Coverage claimed from a configuration page is not coverage.
Sources
references/sources.md in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.
Never
- Retain logs for a window shorter than the time it typically takes to discover an intrusion.
- Store the only copy of a log on the system it describes.
- Ship a detection with no defined response.
- Claim coverage for a technique nobody has tested end to end.
© cbrock84, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/security/skills/detection-and-monitoring of cbrock84/headcount.
- SKILL.md
- references/sources.md
Open the folder on GitHubat commit 98d1c17
Compare with similar skills
Detection And Monitoring next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Detection And Monitoring this skillcbrock84/headcount | 2k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Monitor CInrwl/nx | 29k | 6 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Terraform and OpenTofu Guideagentscope-ai/QwenPaw | 36k | 6 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Vercel Optimize Auditvercel-labs/agent-skills | 32k | 8 repos | ~4.3k | Automated safety check: Pass | None | |
| Analyze GitHub Action Logswithastro/astro | 63k | 1 repos | ~1.3k | Automated safety check: Pass | Custom licence | |
| Openclaw Live Updateropenclaw/openclaw | 392k | — | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
Terraform and OpenTofu Guide
agentscope-ai/QwenPaw
Guidance for writing and testing Terraform and OpenTofu code: module structure, naming, test approaches, CI/CD workflows, state handling and security scanning.
- Official
Vercel Optimize Audit
vercel-labs/agent-skills
Runs a metrics-first audit of a deployed Vercel project, gating investigations on real signals to produce ranked, citation-backed cost and performance recommendations.
- Official
Analyze GitHub Action Logs
withastro/astro
Analyze recent GitHub Actions workflow runs to identify patterns, mistakes, and improvements.
Openclaw Live Updater
openclaw/openclaw
Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.
Docs Learn PR Preview
netdata/netdata
Use only when the user explicitly asks to build, run, preview, inspect, or validate learn.netdata.cloud locally using the contents of a PR or documentation branch before merge.
More from cbrock84/headcount
All 178 skills in this repoAgent Hierarchy
cbrock84/headcount
Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a…
Access And Identity
cbrock84/headcount
Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
Account Based Marketing
cbrock84/headcount
Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group…
Activation
cbrock84/headcount
Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account.
AI ML Governance
cbrock84/headcount
Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire.
AI Research Analyst
cbrock84/headcount
Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit.
Related
Categories
Questions about Detection And Monitoring
What does Detection And Monitoring do?
Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on…. Detection And Monitoring is an agent skill from cbrock84/headcount. Builds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires.
When should I use Detection And Monitoring?
Detection And Monitoring fits situations like: devOps & Cloud work in your project.
How do I install Detection And Monitoring in Claude Code?
Run `npx skills add cbrock84/headcount --skill detection-and-monitoring -a claude-code`. Or copy the skill folder (plugins/security/skills/detection-and-monitoring in cbrock84/headcount) into .claude/skills/detection-and-monitoring in your project. Claude Code loads it when a task matches its description.
How do I install Detection And Monitoring in Codex?
Run `npx skills add cbrock84/headcount --skill detection-and-monitoring -a codex`. Or copy the skill folder (plugins/security/skills/detection-and-monitoring in cbrock84/headcount) into .agents/skills/detection-and-monitoring in your project. Codex loads it when a task matches its description.
Can I use Detection And Monitoring in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cbrock84/headcount --skill detection-and-monitoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/detection-and-monitoring, .gemini/skills/detection-and-monitoring, .github/skills/detection-and-monitoring and .opencode/skills/detection-and-monitoring in your project.
What does Detection And Monitoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Detection And Monitoring is instructions for the agent only.
Does Detection And Monitoring access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Detection And Monitoring safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Detection And Monitoring use?
Detection And Monitoring is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Detection And Monitoring use?
About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 557 tokens, read only when the agent opens those files.
What are the alternatives to Detection And Monitoring?
Skills that share tags, products or a category with Detection And Monitoring: Monitor CI (nrwl/nx, 29k stars), Terraform and OpenTofu Guide (agentscope-ai/QwenPaw, 36k stars), Vercel Optimize Audit (vercel-labs/agent-skills, 32k stars) and Analyze GitHub Action Logs (withastro/astro, 63k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Detection And Monitoring?
cbrock84 (a GitHub user) maintains it in cbrock84/headcount, which has 2,022 GitHub stars. The repository holds 178 skills in this directory. The repository was last updated on September 17, 2026.
Source: cbrock84/headcount on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.