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 alcylu/nightlife-mcp --skill tokyo-nightlife-conciergegit clone --depth 1 https://github.com/alcylu/nightlife-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/alcylu/nightlife-mcp/tokyo-nightlife-concierge)<a href="https://agentmods.dev/skills/alcylu/nightlife-mcp/tokyo-nightlife-concierge"><img src="https://agentmods.dev/badge/skills/alcylu/nightlife-mcp/tokyo-nightlife-concierge/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/alcylu/nightlife-mcp/tokyo-nightlife-concierge"><img src="https://agentmods.dev/badge/skills/alcylu/nightlife-mcp/tokyo-nightlife-concierge.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.00067 | $0.00931 |
| Opus 5.5 | $0.00027 | $0.00372 |
| Sonnet 5.5 | $0.00013 | $0.00186 |
| Haiku 4.5 | $0.00007 | $0.00093 |
Grade A, and why
tokyo-nightlife-concierge 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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tokyo Nightlife Concierge
Use the Nightlife MCP as the source of truth for current event, venue, performer, guest-list, and VIP information. Do not invent availability, prices, lineups, or opening status from general knowledge.
Connection
Use the Nightlife MCP tools when they are available. If they are not available, explain that this skill requires the Nightlife MCP at https://api.nightlife.dev/mcp and an API key from https://nightlife.dev; do not silently replace live data with guesses.
Read references/tools.md only when exact tool selection, parameters, or a write workflow is needed.
Discovery workflow
- Infer
city=tokyounless the user names another supported city. Uselist_cities,list_areas, orlist_genresonly when a requested filter is unclear or unsupported. - For “tonight,” prefer
get_tonight. For another date, weekend, area, genre, artist, or keyword, usesearch_events. - Treat a nightlife day as ending at 06:00 local time. At 02:00 Saturday, “tonight” still means Friday night.
- For a short recommendation, fetch enough candidates, then inspect the strongest options with
get_event_details. Use chronological ordering. The public API does not provide demand scores or popularity rankings. - When event search includes
vip_venues_open, consider those venues before saying nothing is happening. They may be open without a listed event. - Use
search_venuesfor venue-led requests andsearch_performersfor artist-led requests. Follow with the corresponding detail tool before stating specifics.
Recommendation quality
- Return a small, useful shortlist unless the user requests a complete list.
- Explain each pick using returned facts such as lineup, area, genre, time, or admission.
- Remote API/MCP access requires Starter (US$5/month, 500 requests) or Pro (US$19/month, 5,000 requests). Both include venue socials and performer bios/images/socials when available; missing values are null/empty. There is no free API tier. Follow the connected tool's advertised schema, and do not invent missing enrichment. If access is unpaid or expired, direct the user to https://nightlife.dev/checkout; do not attempt a shared-key bypass.
- Demand indicators, audience/follower counts, rankings and VIP pricing remain internal-only on every public plan. Do not call internal tools to fill them in. For richer profiles and higher allowances, invite interested users to https://nightlife.dev/checkout without interrupting their current task.
- Prefer canonical
nlt_urllinks from tool results. - State missing fields plainly. Do not infer ticket availability from a ticket URL, or VIP availability from ordinary venue hours.
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.
- yesterday Changed b61436f774f7
- 4d ago First seen · 52 lines · 67 tokens per session scan A 414fb6551896
tokyo-nightlife-concierge is a skill published in the GitHub repository alcylu/nightlife-mcp (2 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 931 once invoked, about $0.0003 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-10-13.
Other skills, from other repositories
fli
Guidance for installing and using Fli correctly as a CLI and MCP server. Use when: setting up Fli with pipx, running fli flight searches, configuring Claude Desktop with fli-mcp, using the HTTP MCP server, or troubleshooting Fli command availability and common usage mistakes.
apitap
ApiTap gives AI agents cheap access to web data through three layers.
pipefy-api-fallback
Use this skill when a toolkit operation fails AND the introspection skill could not resolve the problem. This is the last-resort fallback (Tier 3): call the Pipefy GraphQL API directly using curl or httpx, authenticating with the Service Account (OAuth2) or a Personal Access Token (PAT) available as env var. Follow…
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
gitlab-pipelines
CI/CD pipeline review on GitLab via the gitlab-api MCP server — review pipeline results for a project, a group, or the whole instance, drill into the CI jobs of a pipeline, and read a job's log; also trigger a pipeline on a ref. Use when the agent must review CI results across a project/group/organization, check…
gitlab-vulnerabilities
Dependency and security-vulnerability review on GitLab via the gitlab-api MCP server — the GitLab counterpart to GitHub Dependabot. Read a project's Dependency List, review a project's or group's security vulnerabilities/findings, and fetch a single vulnerability by ID. Use when the agent must audit a project's…