proactive-security-monitor
Skill501 starsChanged 18 days agoApache-2.0View on GitHub
Proactive supply-chain watch for this repo. Resolves the npm SBOM and batch-queries OSV.dev for freshly-modified advisories (committed fetch.sh), then runs an industry-news pass (CISA KEV, OpenSSF, GitHub Security Lab, Socket, The Hacker News) filtered to this project's stack, and emits both as one findings set for the downstream triager. Use as the daily/scheduled producer half of the proactive-security-monitor → security-monitor-triager chain.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/a11y.mdcCursor rule
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- address-current-branch-reviewSkill
- api-designSkill
- celebration-scene-ideasSkill
- code-review-and-qualitySkill
- create-ticketSkill
- dep-scanSkill
- dep-triageSkill
- dial-docsSkill
- extract-to-libSkill
- figmaSkill
- fix-cve-backportSkill
- git-shipSkill
- i18n-stringsSkill
- lean-verificationSkill
- lib-themingSkill
- monitor-ciSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- refactoring-auditSkill
- chat-release-notesSkill
- responsive-designSkill
- security-monitor-triagerSkill
- snyk-jira-ingestSkill
- snyk-scan-stubSkill
- snyk-triageSkill
- ui-kit-reviewSkill
- nx-generateSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
- nx-generateSkill
- nx-importSkill
- nx-pluginsSkill
- nx-run-tasksSkill
- nx-workspaceSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-exploreSkill
- openspec-proposeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 25
Run exactly this single Bash command (your only Bash allowance):
- Very specific: line 38
If the command is denied or errors before the file exists, the script still writes a status: "failed" envelope.
- Very specific: line 85
Use the Write tool to write stage-output.json again, carrying over payload.findings[] and every other payload key from step 1 unchanged, …
- Very specific: line 92
Update summary to one line covering both passes, e.g.
- Very specific: line 95
Keep any comment_markdown short (≤5 lines, no nested code fences) — long markdown inside JSON is escape-error-prone.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Proactive Security Monitor (producer)
You are the producer in a two-stage proactive-security loop. Your job is to
surface what is newly worth a human's attention this run — freshly-disclosed
dependency advisories and moving-target supply-chain incidents from the
security press — and hand them, un-triaged, to the skeptical
security-monitor-triager stage. You find; the triager validates
reachability. Do not assess exploitability or read application code here — that
is the triager's job, against the correct branch's source.
This is the time-axis complement to the repo's PR-time scanners (Trivy, Dependabot, dependency-review): it pulls fresh advisory + incident signal on a schedule rather than waiting for the next PR or the weekly Dependabot run.
Process
1. Deterministic OSV pass — run the committed script
Run exactly this single Bash command (your only Bash allowance):
bash .claude/skills/proactive-security-monitor/fetch.shIt resolves the npm SBOM from package-lock.json (no install), batch-queries
OSV.dev, keeps advisories modified within the recent window, and writes a
schema-valid stage-output.json with the CVE hits already inlined under
payload.findings[] and an empty payload.news array. Read stage-output.json
to confirm it exists and see what the OSV pass found. Do not rewrite
payload.findings[] — you will only add to this envelope below.
If the command is denied or errors before the file exists, the script still
writes a status: "failed" envelope; in that case stop after reading it.
2. Industry-news pass — your own judgment
Independent of OSV, fetch these sources with WebFetch (look back over the same recent window) and extract items disclosed/updated in that window. The RSS/Atom feeds (e.g. The Hacker News) are broader than supply-chain only — their items span all of infosec — so be especially strict applying the stack + supply-chain filter below; drop generic threat-intel that does not touch this project's stack or a supply-chain/registry/CI vector:
| Source | URL |
| CISA KEV (newly added CVEs) | https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json |
| OpenSSF blog | https://openssf.org/blog/ |
| GitHub Security Lab | https://github.blog/security/ |
| Socket.dev blog | https://socket.dev/blog |
| The Hacker News — RSS feed | https://feeds.feedburner.com/TheHackersNews |
This project's stack — filter every item against it:
Node.js · TypeScript · NestJS 11 · React 19 · react-router 7 ·
Express 5 · Vite · Nx monorepo · helmet · i18next · rxjs · mime-types ·
reflect-metadata · npm / npm registry · GitHub Actions toolchain
(epam/ai-dial-ci reusable workflows, actions/*, step-security/harden-runner).
Classify every item into exactly one tag:
- RELEVANT — names a package in the SBOM, or a Node/npm/TypeScript/React/NestJS/Vite/Nx-specific incident, or an npm-registry or GitHub-Actions-toolchain attack.
- TANGENTIAL — a supply-chain technique or registry-abuse case in another ecosystem (PyPI, RubyGems, Maven, Go, etc.) that plausibly translates to this stack. Include only with a one-sentence translation rationale. Default to IGNORE if unsure.
- IGNORE — audited, not applicable. Keep title + source so the filter is auditable; no analysis.
Record every fetch deterministically. For each source in the table above,
note the WebFetch outcome so coverage gaps are a fact, not model narration. You
will emit these in step 3 as payload.news_sources[] — one entry per table row,
each {source, url, attempted, ok, item_count, note?}:
- A WebFetch that errors (HTTP 403, timeout, unreachable, unparseable) ⇒
{attempted: true, ok: false, item_count: 0, note: "<reason, e.g. HTTP 403 bot block>"}. - A WebFetch that succeeds but yields no in-window items ⇒
{attempted: true, ok: true, item_count: 0}(a real, reachable-but-empty source — not a coverage gap). - A WebFetch that succeeds with items ⇒
{attempted: true, ok: true, item_count: <N items extracted from that source>}.
item_count is the count of items extracted from that source before the
RELEVANT/TANGENTIAL/IGNORE filter, so a source can be ok: true with a positive
item_count even if every item ends up IGNORE.
3. Enrich the envelope (preserve the OSV findings)
Use the Write tool to write stage-output.json again, carrying over
payload.findings[] and every other payload key from step 1 unchanged, and
adding the news pass:
payload.news— array of{tag, title, source, url, date, rationale?, stack_hit?, suggested_action?}for RELEVANT and TANGENTIAL items (and an auditable list of IGNORE titles underpayload.news_ignored).payload.news_sources— array with one entry per source row in the step-2 table, each{source, url, attempted, ok, item_count, note?}, populated from the per-source WebFetch outcomes recorded in step 2. This makes coverage gaps deterministic: a source that returned 403/error appears asok: falsewith anote, distinct from a reachable source that simply had no in-window items (ok: true, item_count: 0). The triager reads this instead of inferring reach from prose.- For each RELEVANT item that maps to a concrete repo action (e.g. "SHA-pin a mutable
uses:ref", "confirm token rotation"), add asuggested_action. - Update
summaryto one line covering both passes, e.g."OSV: 2 in-window; News: 3 RELEVANT, 4 TANGENTIAL (incl. GitHub Actions campaign)." - Set
statustopassed_with_findingsif there is any OSV finding OR any RELEVANT/TANGENTIAL news item; otherwisepassed.
Keep any comment_markdown short (≤5 lines, no nested code fences) — long
markdown inside JSON is escape-error-prone. The downstream triager reads the
structured payload, not prose.
Output
One stage-output.json at repo root:
{stage, status, summary, payload:{findings[], news[], news_ignored[], news_sources[], ...}}.
The OSV findings[] come from fetch.sh; you add news[], news_ignored[], and
news_sources[] (one {source, url, attempted, ok, item_count, note?} entry per
step-2 source, recording each WebFetch outcome so coverage gaps are deterministic).
The triager stage consumes this whole payload.
Required tools
Bash(bash .claude/skills/proactive-security-monitor/fetch.sh:*), Read,
WebFetch, Skill. (Write is granted by the platform.)
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

