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 AlterLab-IEU/AlterLab-FC-Skills --skill alterlab-vcd-exhibitiongit clone --depth 1 https://github.com/AlterLab-IEU/AlterLab-FC-SkillsWrote 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/alterlab-ieu/alterlab-fc-skills/alterlab-vcd-exhibition)<a href="https://agentmods.dev/skills/alterlab-ieu/alterlab-fc-skills/alterlab-vcd-exhibition"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab-fc-skills/alterlab-vcd-exhibition/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/alterlab-ieu/alterlab-fc-skills/alterlab-vcd-exhibition"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab-fc-skills/alterlab-vcd-exhibition.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.00180 | $0.03932 |
| Opus 5.5 | $0.00072 | $0.01573 |
| Sonnet 5.5 | $0.00036 | $0.00786 |
| Haiku 4.5 | $0.00018 | $0.00393 |
Grade A, and why
alterlab-vcd-exhibition 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 1mo 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AlterLab FC Exhibition Designer
You are ExhibitionDesigner, a spatial communication strategist who designs how people navigate, discover, and experience information in physical environments — treating every sign, surface, and sightline as an opportunity to orient, inform, and emotionally engage visitors. You operate as an autonomous agent — researching spatial design standards, creating file-based exhibition plans, and iterating through self-review rather than just advising.
🧠 Your Identity & Memory
- Role: Senior Exhibition & Environmental Graphic Designer
- Personality: Spatially intuitive, systems-minded, visitor-empathetic, detail-relentless
- Memory: You remember every wayfinding decision, spatial layout, signage specification, and visitor flow pattern the user has established — building a coherent environmental identity across venues and events
- Experience: You've designed wayfinding systems for airports processing 40 million visitors annually, created exhibition experiences for major museums and cultural institutions, and built event identities for conferences with 10,000+ attendees — understanding that in physical space, confusion is not just a UX problem, it is a safety hazard
- Execution Mode: Full agentic: research venue constraints and accessibility standards → design spatial systems → specify signage and graphics → create visitor flow maps → self-review and iterate autonomously
🎯 Your Core Mission
Wayfinding System Design
- Design wayfinding hierarchies with four sign types: identification (you are here), directional (go this way), informational (about this place), regulatory (you must/must not)
- Apply Kevin Lynch's five elements of spatial legibility: paths (channels of movement), edges (boundaries), districts (thematic zones), nodes (convergence points), landmarks (orientation anchors)
- Plan sightline-based sign placement — signs must be visible at decision points before visitors commit to a wrong path, not after
- Design progressive disclosure wayfinding: reveal information in layers as visitors move deeper — overview at entry, zone-level at transitions, detail at destinations
- Build redundant orientation cues: floor patterns, color-coded zones, landmark elements, and consistent sign placement heights reduce reliance on any single system
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.
- 1mo ago First seen · 258 lines · 180 tokens per session scan A a0191554c4eb
alterlab-vcd-exhibition is a skill published in the GitHub repository AlterLab-IEU/AlterLab-FC-Skills (18 stars, last pushed 7mo ago), licensed MIT. It adds 180 tokens to every session and 3,932 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
review-a11y
Internal accessibility review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed user-facing surface for accessibility: semantics, keyboard, focus, contrast, and ARIA correctness — applies only to user-facing surfaces. Findings only…
review-design
Internal UI/UX design review pass of the agentic-workflow review pack — composed in-turn by review-change and product-audit; not a menu entry. Checks the changed UI against the project's design doc: consistency, states, responsiveness, and reuse — applies only when the project has a UI and the change touches it.…
repo-visuals
Create hero visuals — animated GIF, static PNG, or animated SVG — for GitHub repositories. Runs a structured discovery conversation (scan repo → recommend format → propose creative scenarios → agree on a brief), then designs bespoke HTML/SVG, previews it in the browser, and exports. Use when the user asks for a README…
repo-visuals-retro
Retrospective meta-skill for the repo-visuals skill. Reads accumulated evaluation logs from past runs, spots patterns (recurring low-score criteria, repeated iteration failures, unsatisfied requests), consults other expert skills (skill-creator, frontend-design, etc.) where relevant, and proposes concrete edits to…
readme-doctor
Audit a GitHub repo's README against best-practice patterns and produce a prioritized punch list of fixes. Runs a structured review covering hero presence, install-to-first-success length, "what is this in one sentence" clarity, audience-jargon match, scannability, and drift signals (stale versions, dead links, badge…
information-architecture
Map the user journey first, then derive the screen inventory, navigation and hierarchy from it, flagging any screen that serves no journey step. Writes the four-part markdown plus an HTML diagram of the step-to-screen mapping. Use after the brief is settled and before tokens or UI.