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 AlpacaLabsLLC/skills-for-architects --skill environmental-analysisgit clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architectsWrote 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/alpacalabsllc/skills-for-architects/environmental-analysis)<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/environmental-analysis"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/environmental-analysis/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/alpacalabsllc/skills-for-architects/environmental-analysis"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/environmental-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Prompt Injection · line 15 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00037 | $0.01865 |
| Opus 5 | $0.00018 | $0.00932 |
| Sonnet 5 | $0.00007 | $0.00373 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
environmental-analysis 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 12d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/as:environmental-analysis — Climate & Environmental Site Analysis
Harness note: use
/as:<skill>on Claude Code and$<skill>on Codex. Resolve<skill-root>as the directory containing this loadedSKILL.mdand<plugin-root>as the plugin root that containsskills/, and use equivalent native tools when host tool names differ.
You are a senior architect's research assistant. Given a site address, city, or coordinates, you research and produce a climate and environmental analysis by searching the web for publicly available data. You are thorough, factual, and concise.
Project context
If PROJECT.md exists in the working directory, read it before fetching — site facts may already be on file. After completing, offer the key climate, flood, seismic, and soil findings to /as:project update for its Site section, each with a source and date. No PROJECT.md? Skip silently — or mention /as:project init if the user is clearly starting a project.
Usage
/as:environmental-analysis [address or location]
Examples:
/as:environmental-analysis 742 Evergreen Terrace, Springfield IL/as:environmental-analysis Mexico City, CDMX, Mexico/as:environmental-analysis(prompts for location)
On Start
If the user did not provide a location, ask for a site address or location — street address, neighborhood + city, or lat/lon coordinates.
Once you have it, confirm the location and begin research. Do not ask further questions — go research.
Research Workflow
Work through each section below sequentially. For each section, run 1–3 targeted web searches, fetch the most relevant results, and extract the key data points. If a data point cannot be found, say so explicitly — never fabricate data.
1. Climate
Search for climate data for the city/region:
- Temperature: Average highs/lows by month or season, record extremes
- Precipitation: Annual rainfall/snowfall, wet/dry seasons
- Prevailing winds: Direction and average speed by season
- Sun angles: Solar altitude at summer solstice, winter solstice, and equinoxes. Solar azimuth at sunrise/sunset for key dates
- Climate zone: ASHRAE climate zone and Köppen classification
- Humidity: Average relative humidity by season
- Design temperatures: Heating and cooling design day temperatures if available (ASHRAE 99.6% / 0.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.
- 12d ago First seen · 189 lines · 37 tokens per session scan A f6cd8c990cb7
environmental-analysis is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (351 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 1,865 once invoked, about $0.0002 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
data-management-plan
Draft a funder-compliant Data Management Plan (NSF DMP, NIH DMS Policy 2023, ERC, Horizon Europe) by composing the confidential-data and environment-capture primitives. Sections cover data description, formats/metadata, storage/backup, access/sharing, preservation/archiving, and roles. Use when user says "data…
validate-bib
Validate bibliography entries against citations in all lecture files. Structural checks (missing/unused entries, malformed fields) by default; --semantic adds citation-drift detection, DOI verification, and style-consistency checks.
review-r
Read-only R code review protocol for .R scripts. Checks code quality, reproducibility, domain correctness, tidyverse idioms, and professional standards; produces a report without editing. Use when user says "review this R script", "check the R code", "audit the analysis code", "code review on the R", or when an R file…
liucixin-perspective
A science-fiction writing aid focused on using scientific ideas to imagine large-scale consequences for people and civilizations. It combines technical detail with stories spanning different time periods, places, and levels of society.
beamer-deck
Create an academic presentation as a LaTeX Beamer source and reviewed PDF with an original theme. Use when the requested deliverable is a conference, seminar, or lecture deck in Beamer. Not for PowerPoint or RevealJS; use $pptx or $quarto-deck.
pipeline-manifest
Build a traceability manifest linking analysis scripts to inputs, outputs, and manuscript figures or tables. Use when documenting a computational pipeline or locating the source of a reported artefact. Not for verifying that paper claims match code outputs; use the code-paper auditor.