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 agentmods add commands/vishnu2kmohan/mcp-server-langgraph/setup-envgit clone --depth 1 https://github.com/vishnu2kmohan/mcp-server-langgraphWrote 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/vishnu2kmohan/mcp-server-langgraph/setup-env)<a href="https://agentmods.dev/commands/vishnu2kmohan/mcp-server-langgraph/setup-env"><img src="https://agentmods.dev/badge/commands/vishnu2kmohan/mcp-server-langgraph/setup-env.svg" alt="Measured on agentmods" 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 | $0.00009 | $0.00745 |
| Opus 5 | $0.00005 | $0.00373 |
| Sonnet 5 | $0.00002 | $0.00149 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
setup-env 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete Environment Setup
Execute the complete development environment setup from scratch.
Setup Steps
-
Install Dependencies
make install-devInstalls:
- Python dependencies via uv
- Development tools
- Test dependencies
-
Start Infrastructure
make setup-infraStarts Docker Compose services:
- OpenFGA (authorization)
- PostgreSQL (OpenFGA storage)
- Keycloak (SSO/authentication)
- Redis (session storage)
- Jaeger (distributed tracing)
- Prometheus (metrics)
- Grafana (visualization)
- Qdrant (vector database)
-
Configure OpenFGA
make setup-openfgaSets up:
- Creates OpenFGA store
- Loads authorization model
- Displays OPENFGA_STORE_ID and OPENFGA_MODEL_ID
-
Configure Keycloak
make setup-keycloakSets up:
- Creates realm and clients
- Configures users and roles
- Displays KEYCLOAK_CLIENT_SECRET
-
Environment Configuration
cp .env.example .envThen manually update .env with:
- OPENFGA_STORE_ID (from step 3)
- OPENFGA_MODEL_ID (from step 3)
- KEYCLOAK_CLIENT_SECRET (from step 4)
- GOOGLE_API_KEY (from https://aistudio.google.com/apikey)
- Optional: ANTHROPIC_API_KEY, OPENAI_API_KEY
-
Restart Services
docker-compose restart agent -
Verify Setup
make health-check make test-unit
Quick Start Alternative
For a faster automated setup:
make dev-setup
This runs steps 1-4 automatically, but you'll still need to:
- Update .env with IDs/secrets
- Restart agent service
Post-Setup Verification
-
Check Services
- OpenFGA: http://localhost:8080
- OpenFGA Playground: http://localhost:3001
- Keycloak: http://localhost:8081 (admin/admin)
- Jaeger: http://localhost:16686
- Prometheus: http://localhost:9090
- Grafana: http://localhost:3000 (admin/admin)
-
Run Tests
make test-unit
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.
- 3d ago First seen · 128 lines · 9 tokens per session scan A ba0c3bcd60c8
setup-env is a command published in the GitHub repository vishnu2kmohan/mcp-server-langgraph (4 stars, last pushed 10d ago), licensed MIT. It adds 9 tokens to every session and 745 once invoked, about $0.0000 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 commands, from other repositories
hal-voice-toggle
Toggle HAL 9000 voice clips on or off.
deps-age
Analyze dependency freshness and maintenance activity.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
plan-delegate
Execution: work a roadmap as supervisor, brief an implementation agent per item, verify its work independently, then record and commit it.
designer
UI/UX design with Memory coordination for consistent experiences.
pipeline-generate
You are a senior DevOps & Cloud Infrastructure specialist. The user needs help with pipeline generate in the context of ci/cd pipelines, container orchestration, iac, monitoring and incident response.