site-history

site-history is a skill for Claude Code from AlpacaLabsLLC/skills-for-architects. It costs 53 tokens per session (1,503 once invoked), scanned A, original, MIT.

A research skill for understanding the history and surroundings of a building site from an address, city, or map coordinates. It covers nearby uses, architectural character, landmarks, business activity, and planned development.

In plain words
What is it for?
Use it to research a site’s local history, nearby places, architectural setting, commercial activity, and proposed development using public information.
Why use it?
It gathers neighborhood context that may be difficult to assemble from a single map or property listing.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code; mentions Codex.

Part of the as plugin — 46 skills, 7 agents, 3 hooks shipped together

Good fit Use it to research a site’s local history, nearby places, architectural setting, commercial activity, and proposed development using public information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alpacalabsllc/skills-for-architects/site-history
Install

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.

Any agent
npx skills add AlpacaLabsLLC/skills-for-architects --skill site-history
Clone the repo
git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects

Made for: Claude Code.

Or install as, the plugin that ships this one along with the rest of its 46 skills, 7 agents, 3 hooks.

Wrote 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.

agentmods badge for site-history

README.md
[![agentmods](https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/site-history/github.svg)](https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/site-history)
Your own site
<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/site-history"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/site-history/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.

agentmods 80×15 button for site-history

Your own site · 80×15
<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/site-history"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/site-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,503 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00053 $0.01503
Opus 5 $0.00026 $0.00751
Sonnet 5 $0.00011 $0.00301
Haiku 4.5 $0.00005 $0.00150

Measured 12d ago against content hash 5dcb4e7c8819, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

site-history 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.

skills/site-history/SKILL.md · 162 lines

How it starts

The opening of the file, as written. The whole thing — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/as:site-history — Neighborhood Context & History

Harness note: use /as:<skill> on Claude Code and $<skill> on Codex. Resolve <skill-root> as the directory containing this loaded SKILL.md and <plugin-root> as the plugin root that contains skills/, 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 neighborhood context and history 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 neighborhood-context 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:site-history [address or location]

Examples:

  • /as:site-history 742 Evergreen Terrace, Springfield IL
  • /as:site-history Mexico City, CDMX, Mexico
  • /as:site-history (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

Run 3–5 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.

Neighborhood Context

Search for information about the immediate surroundings:

  • Adjacent land uses: What's north, south, east, west of the site
  • Neighborhood character: Architectural style, building ages, density pattern, streetscape
  • Historic districts: Landmark designations, historic district boundaries, contributing building status
  • Neighborhood history: How the area developed, key periods of construction, demographic shifts
  • Landmarks: Notable buildings, parks, institutions within ~1 km
  • Commercial activity: Retail corridors, restaurants, services, nightlife nearby
  • Planned development: Major projects approved or under construction in the area
  • Community: Neighborhood associations, community boards, local governance
  • Safety: General crime context if publicly available

Read the full file on GitHub · 162 lines

Files

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.

Changes

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.

  1. 12d ago First seen · 162 lines · 53 tokens per session scan A 5dcb4e7c8819

Subscribe to this mod's changes

site-history is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (353 stars, last pushed 8d ago), licensed MIT. It adds 53 tokens to every session and 1,503 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

cre-asset-management

CRE Asset Management analysis suite — 9 specialist skills for post-acquisition multifamily operations including annual budgeting, monthly variance analysis, rent collection, renewal decisions, lease-up tracking, capex execution, NOI improvement, hold/sell/refi scenario analysis, and quarterly asset review memos.

ahacker-1/cre-agent-skills · 62 tokens

cre-development

CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.

ahacker-1/cre-agent-skills · 52 tokens

cre-due-diligence

CRE Due Diligence analysis suite — 7 specialist skills for multifamily property analysis including rent roll validation, expense benchmarking, market study, physical inspection, environmental review, title review, and tenant credit assessment.

ahacker-1/cre-agent-skills · 49 tokens

cre-legal

CRE Legal review suite — 6 specialist skills for PSA review, title & survey analysis, estoppel tracking, loan document review, insurance coordination, and transfer document preparation for multifamily acquisitions.

ahacker-1/cre-agent-skills · 42 tokens

cre-office

CRE Office analysis suite - 8 specialist skills for U.S. office acquisitions, refinancings, lease-up, tenant credit, TI/LC underwriting, financing fit, and investment committee memo writing.

ahacker-1/cre-agent-skills · 43 tokens

cre-lender-credit

CRE Lender/Credit analysis suite - 8 specialist skills for U.S. CRE loan screening and sizing, sponsor and appraisal review, credit memo writing, annual risk rating, covenant and watchlist monitoring, problem loans, and portfolio stress testing.

ahacker-1/cre-agent-skills · 54 tokens