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.
git clone --depth 1 https://github.com/Azure-Samples/mcp-agent-langchainjsWrote 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/commands/azure-samples/mcp-agent-langchainjs/enable-beer)<a href="https://agentmods.dev/commands/azure-samples/mcp-agent-langchainjs/enable-beer"><img src="https://agentmods.dev/badge/commands/azure-samples/mcp-agent-langchainjs/enable-beer/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/commands/azure-samples/mcp-agent-langchainjs/enable-beer"><img src="https://agentmods.dev/badge/commands/azure-samples/mcp-agent-langchainjs/enable-beer.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.00000 | $0.00132 |
| Opus 5.5 | $0.00000 | $0.00053 |
| Sonnet 5.5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
enable-beer 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 today.
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
Task
- Run
azd env set ENABLE_BEERS truefrom the root of the project in a terminal. If no environment has been set up yet, you can runazd env newfirst to create a new environment, then run the command to set the variable. - Enable the Beer MCP service by uncommenting
beer-mcpinazure.yaml - Rename
_start:beertostart:beerin rootpackage.json
Once you have done the above steps, just prompt the user to run the azd up command to deploy the infrastructure and services to complete the setup.
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.
- today First seen · 8 lines · 0 tokens per session scan A 4ea6b0f14be2
enable-beer is a command published in the GitHub repository Azure-Samples/mcp-agent-langchainjs (204 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 132 tokens. 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-29.
Other commands, from other repositories
setup-gemini.en
Command "setup-gemini.en" from minicoohei/ai-agent-camp, covering gemini api setup, step 0: check setup progress, what you'll do in this session, readiness check and step 1: open google ai studio in the browser.
validate-pipeline
Validate data pipeline configuration and data quality rules.
ml-run-review
Review a machine learning training run or experiment configuration for soundness, reproducibility, and evaluation rigor.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.