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 neverinfamous/memory-journal-mcp --skill rendergit clone --depth 1 https://github.com/neverinfamous/memory-journal-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/neverinfamous/memory-journal-mcp/render)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/render"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/render/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/neverinfamous/memory-journal-mcp/render"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/render.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.00089 | $0.00616 |
| Opus 5 | $0.00044 | $0.00308 |
| Sonnet 5 | $0.00018 | $0.00123 |
| Haiku 4.5 | $0.00009 | $0.00062 |
Grade A, and why
render 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 10d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Render Deployment Best Practices
Guidelines for managing infrastructure and deploying applications on the Render platform.
1. Infrastructure as Code (render.yaml)
- Blueprints: Always use Render Blueprints (
render.yaml) to define your infrastructure. This enables GitOps, ensures reproducibility, and prevents configuration drift in the dashboard. - Sync Environments: Define multiple environments (e.g., staging, production) using environment-specific branches and
render.yamlconfigurations.
2. Web Services & Background Workers
- Health Checks: Always define a
healthCheckPathinrender.yaml. Render uses this to ensure zero-downtime deployments. If the health check fails, the new deploy is aborted and the old version remains live. - Start Commands: Ensure your start command starts a production-ready web server (e.g.,
gunicorn,pm2, or Node.jsserver.js). Do not use development servers (e.g.,npm run dev,flask run) in production. - Background Workers: Separate long-running tasks into Background Workers. Background Workers do not have exposed HTTP ports and won't be killed for failing to bind to a port (unlike Web Services).
3. Databases (PostgreSQL & Redis)
- Internal Connections: Always connect Web Services to Databases using the Internal Database URL. This traffic stays within Render's private network, which is faster and vastly more secure.
- External Access: Restrict external database access. If you must connect externally (e.g., for local debugging), use the Access Control list to whitelist specific IP addresses rather than allowing
0.0.0.0/0. - Migrations: Execute database migrations using the
preDeployCommand. This runs before the new code goes live, ensuring the schema is ready for the new application version.
4. Environment Variables & Secrets
- Secret Files: For files like
.env, use Render's Secret Files feature. Reference them inrender.yaml. - Env Var Groups: Group common environment variables (like AWS credentials or API keys used across multiple services) into Environment Groups and link them to services in your Blueprint.
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.
- 10d ago First seen · 36 lines · 89 tokens per session scan A 3ec5f9b244df
render is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 616 once invoked, about $0.0004 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 skills, from other repositories
maintain-splash-pages
The Lossless Group's pattern for repo-level splash pages — small Astro sites at /splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy…
skill-creator
Generate a new skill from a plain-language description — decides invocation control, arguments, and context cost, then scaffolds, validates, and tests it.
tech-writing
Write professional technical documents — requirements/PRD, tech spec/design doc, low-level design, decision records, and trade-off analysis — at a formality tier matched to the task. Grounds every claim in real code or a cited source, marks what it could not verify, and refuses to pad. Use when asked to write/update a…
context-end
Close a workspace session by reviewing a proposed summary, recording approved outcomes, updating state and decisions, and checking repository safety. Use only when the user explicitly asks to end, close, or hand off the current session.
context-setup
Build, import, or refresh this workspace's identity, project, reusable-workflow, and weekly-state files through a guided review. Use only when the user explicitly asks to initialize or redo workspace context.
context-start
Load this workspace's current state, recent decisions, blockers, priorities, and session continuity, then give a concise briefing. Use only when the user explicitly asks to begin or resume a workspace session.