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.
npx skills add dmoskov/sharedskills --skill environmental-scangit clone --depth 1 https://github.com/dmoskov/sharedskillsWrote 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/dmoskov/sharedskills/environmental-scan)<a href="https://agentmods.dev/skills/dmoskov/sharedskills/environmental-scan"><img src="https://agentmods.dev/badge/skills/dmoskov/sharedskills/environmental-scan/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/dmoskov/sharedskills/environmental-scan"><img src="https://agentmods.dev/badge/skills/dmoskov/sharedskills/environmental-scan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00032 | $0.00535 |
| Opus 5.5 | $0.00013 | $0.00214 |
| Sonnet 5.5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
environmental-scan 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 2mo 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.
What it actually says
Environmental Scanning Skill
Look outward: find security advisories, breaking upstream changes, and relevant new releases/research that affect the current project, and produce a severity-ranked intelligence report. Runs entirely from the session using web search/fetch — no database, feeds infrastructure, or scheduled jobs required.
When to Use
- Periodically (weekly is a good cadence) on any actively developed project
- Before upgrading dependencies or planning a maintenance window
- After security news breaks and you want to know "are we affected?"
- When starting work on a project that's been dormant for a while
Scan Categories
| Category | What to check | Primary sources |
|---|---|---|
| Security | CVEs/advisories for your actual dependencies | OSV.dev, GitHub Advisories, NVD, RustSec, PyPA |
| API changes | Breaking changes in SDKs/APIs the project calls | Vendor changelogs, release notes |
| Dependencies | Major-version releases, deprecations, EOL notices | PyPI, npm, crates.io registries |
| Research | New techniques relevant to what the project does | arXiv, vendor engineering blogs |
Workflow
Follow prompts/scan.md. Quick summary:
- Inventory — read the project's manifests (requirements.txt, package.json, Cargo.toml, go.mod, ...) to build the real dependency list with pinned versions
- Sweep — check each category against the sources above, scoped to that inventory
- Filter — keep only findings that actually affect the versions in use
- Report — severity-ranked markdown report with concrete remediation steps
Output
A markdown report (printed, or written to a file if the user asks) with sections:
Critical / High / Notable / Informational. Every finding cites its source URL and
names the affected file (e.g. requirements.txt: aiohttp 3.9.1 → CVE-2024-XXXX, fixed in 3.9.4).
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.
- 2mo ago First seen · 58 lines · 32 tokens per session scan A 9000790fe1ee
environmental-scan is a skill published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 535 once invoked, about $0.0001 per session on Opus 5.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-31.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…