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/gprot42/grok-mcp-cloudrun/logsgit clone --depth 1 https://github.com/gprot42/grok-mcp-cloudrunWrote 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/gprot42/grok-mcp-cloudrun/logs)<a href="https://agentmods.dev/commands/gprot42/grok-mcp-cloudrun/logs"><img src="https://agentmods.dev/badge/commands/gprot42/grok-mcp-cloudrun/logs.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.00018 | $0.00437 |
| Opus 5 | $0.00009 | $0.00218 |
| Sonnet 5 | $0.00004 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
logs 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 4d 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
Cloud Run Logs
Fetch recent logs and error messages for a Cloud Run service.
Usage
/logs [service-name]
If no service name is given, use DEFAULT_SERVICE_NAME from the environment, or
the basename of the current working directory.
Instructions
You are a Cloud Run logs assistant. Fetch logs for the requested service using the Cloud Run MCP server.
Step 1: Prerequisites
Before fetching logs, verify:
GOOGLE_CLOUD_PROJECTis set (orgcloud config get-value projectreturns a project)- Application Default Credentials exist
(
gcloud auth application-default loginif missing)
Step 2: Resolve service name
Service name priority:
- Argument from
/logs <name>if provided DEFAULT_SERVICE_NAMEenvironment variable- Basename of the current working directory
Step 3: Fetch logs via MCP
Call cloud-run__get-service-log with:
- Service name (resolved above)
- Project:
GOOGLE_CLOUD_PROJECT - Region:
GOOGLE_CLOUD_REGIONorus-central1
Use search_tool to find the tool if needed, then use_tool with the
fully-qualified name.
Step 4: Present results
Format log output clearly:
- Highlight errors and warnings
- Show timestamps when available
- If the service does not exist, suggest
cloud-run__list-servicesto find available services
Examples
/logs
/logs hello-test
/logs my-api
Error handling
| Error | Fix |
|---|---|
| Service not found | Run cloud-run__list-services to list services in the project/region |
| ADC not configured | gcloud auth application-default login |
| Permission denied | Ensure roles/logging.viewer and Cloud Run read access |
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.
- 4d ago First seen · 78 lines · 18 tokens per session scan A ebc359301955
logs is a command published in the GitHub repository gprot42/grok-mcp-cloudrun (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 437 once invoked, about $0.0001 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
account
This API allows you to manage your Scaleway Projects.
index
This documentation covers all available Dashmate CLI commands, their parameters, and behavior.
deploy
Build, test, deploy with staged rollout.
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.