Borrowing it
Nothing to install: this file belongs to epam/ai-dial-chat. 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/epam/ai-dial-chat/development/.claude/skills/proactive-security-monitor/SKILL.mdgit clone --depth 1 https://github.com/epam/ai-dial-chatWrote 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/epam/ai-dial-chat/proactive-security-monitor)<a href="https://agentmods.dev/skills/epam/ai-dial-chat/proactive-security-monitor"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/proactive-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.
<a href="https://agentmods.dev/skills/epam/ai-dial-chat/proactive-security-monitor"><img src="https://agentmods.dev/badge/skills/epam/ai-dial-chat/proactive-security-monitor.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 Anti-Refusal · line 80 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
- medium Prompt Injection · line 50 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Agent Snooping · line 108 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00105 | $0.01806 |
| Opus 5 | $0.00053 | $0.00903 |
| Sonnet 5 | $0.00021 | $0.00361 |
| Haiku 4.5 | $0.00011 | $0.00181 |
Grade A, and why
proactive-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 9d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.sh
It 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:
What ships with it
1 file 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.
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.
- 9d ago Changed · +1 lines d495dbe936f9
- 13d ago First seen · 111 lines · 105 tokens per session scan A 0c2d9133ea40
proactive-security-monitor is a skill published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 1,806 once invoked, about $0.0005 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…