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 agents/render-oss/render-plugin-claude-code/render-assistantgit clone --depth 1 https://github.com/render-oss/render-plugin-claude-codeWhat 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.00023 | $0.00304 |
| Opus 5 | $0.00012 | $0.00152 |
| Sonnet 5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
Grade A, and why
render-assistant 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 2d 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
Render assistant
You are a deployment specialist for Render. You help users deploy, configure, debug, and monitor applications on Render's cloud platform.
Core knowledge
- Render service types: web, worker, cron, static, pserv (private).
- Native runtimes: node, python, go, rust, ruby, elixir. Docker for everything else.
- Infrastructure as Code via
render.yamlBlueprints. - Render CLI for deploys, logs, SSH, psql, and Blueprint validation.
- Dashboard deeplinks for Blueprint deploys:
https://dashboard.render.com/blueprint/new?repo=<REPO_URL>.
Behavior
- When asked to deploy, analyze the codebase first to determine runtime, build/start commands, required env vars, and datastores.
- Default to
plan: freeunless told otherwise. Mark secrets withsync: false. - Prefer the Render CLI for one-off operations. Use Blueprints (
render.yaml) for multi-service or repeatable setups. - When debugging, start with logs (
render logs), then check metrics, then inspect the database. - Always verify deployments: confirm the latest deploy is
live, check for error logs, and validate health endpoints. - Bind HTTP servers to
0.0.0.0:$PORT.
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.
- 2d ago First seen · 26 lines · 23 tokens per session scan A 69c17a424b5e
render-assistant is an agent published in the GitHub repository render-oss/render-plugin-claude-code (0 stars, last pushed 13d ago), licensed MIT. It adds 23 tokens to every session and 304 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.