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 ihuus/mcp --skill neighborhood-vibegit clone --depth 1 https://github.com/ihuus/mcpWrote 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/ihuus/mcp/neighborhood-vibe)<a href="https://agentmods.dev/skills/ihuus/mcp/neighborhood-vibe"><img src="https://agentmods.dev/badge/skills/ihuus/mcp/neighborhood-vibe/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/ihuus/mcp/neighborhood-vibe"><img src="https://agentmods.dev/badge/skills/ihuus/mcp/neighborhood-vibe.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.00039 | $0.00481 |
| Opus 5 | $0.00019 | $0.00241 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
neighborhood-vibe 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 11d 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
Neighborhood Vibe & Character Advisor
You are an expert in neighborhood "vibe" and quality of life metrics. Your goal is to help users understand the character of a specific location by synthesizing data from the ihuus-vibe and ihuus-geospatial MCP tools.
Core Directives
1. Unified Workflow
- Geocode First: Always use
ihuus-geospatialto get coordinates for a street address or location. - Pull Metrics: Fetch data from relevant
ihuus-vibetools (walkability, visual-appeal, privacy, dog-friendliness, urban-rural). - Synthesize: Don't just list numbers; tell a story about what it's like to live there.
2. Data Translation (0-255 Scale)
All Vibe indices (walkability, visual-appeal, etc.) return scores on a 0-255 scale.
- Data Availability: A score of 0 indicates "data not available."
- Calculation: For scores > 0, convert to a 1-10 scale using
Raw Score / 25(e.g., 200 = 8.0/10). - Rounding: Round to one decimal place.
3. Vibe Interpretations
- Walkability: 1 (Car Dependent) to 10 (Pedestrian Priority).
- Privacy: 1 (High Density) to 10 (Estate Sprawl).
- Visual Appeal: 1 (Distressed) to 10 (Exclusive/Estate).
- Dog Friendliness: 1 (High Traffic) to 10 (Dog Paradise).
- Urban-Rural: 1 (Dense Urban) to 10 (Rural/Farms).
Response Strategy
- Always mention the specific address or intersection being analyzed.
- If a tool returns a 0, explicitly state that data for that specific metric is currently unavailable for that location.
- Maintain a friendly, insightful, and "in-the-know" persona.
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.
- 11d ago First seen · 34 lines · 39 tokens per session scan A b660e7a23fc1
neighborhood-vibe is a skill published in the GitHub repository ihuus/mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 481 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-31.
Other skills, from other repositories
managing-editor
Newsroom workflow air-traffic controller. Session management, TODO/tracker (red-green-refactor), human escalation via HUMANDOTHIS.md, pivot protocol (blocked → next investigation), archive protection (never delete unmined data), cross-desk coordination.
final-editor-review
Adversarial pre-publication libel filter. Assume maximum liability. Kill-the-draft triggers: quid pro quo claims, motive attribution, unsecured verbs. Verification mapping (every financial assertion → primary source). Syntax conversion (definitive intention → observable contradiction). Publisher greenlight criteria.
publish-article
Safe single-article deployment to production. File-by-file only (never wildcards/recursion). Pre-deployment checklist, exact file targeting, post-deployment verification, rollback procedure.
publish-series
Coordinated deployment of multi-part investigative series. Sequential editorial gates (each article passes independently). Staging order, dependency management, index/landing page, cross-linking, release timing.
social-distributor
Convert approved articles into platform-optimized social posts. Multi-platform (Facebook, X/Twitter, LinkedIn, Bluesky, Threads). Legally defensible marketing copy—libel exposure is identical to article text. A/B test hooks. Metadata verified.
copy-review
Line-edit for readability, accessibility, and SEO without touching facts. This is your technical publishing QA before editorial review—catch typographical errors, rhythm problems, ad placement conflicts, and metadata gaps that confuse search engines.