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 azuregit 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/azure)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/azure"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/azure/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/azure"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/azure.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.00068 | $0.00609 |
| Opus 5.5 | $0.00027 | $0.00244 |
| Sonnet 5.5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
azure 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 2mo 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Microsoft Azure Best Practices
STOP. Your knowledge of Azure may be outdated. Prefer retrieval over pre-training for any version-sensitive Azure configuration. Fetch current documentation when in doubt.
Standards for deploying and managing workloads securely on Microsoft Azure.
1. Identity & Access (Azure Entra ID / Active Directory)
- Managed Identities: Use System-Assigned or User-Assigned Managed Identities for Azure resources (VMs, App Services, Functions) to authenticate to other Azure services (Key Vault, SQL, Storage) without managing credentials.
- RBAC: Use Azure Role-Based Access Control. Assign roles to Entra ID Groups rather than individual users to simplify lifecycle management.
- Key Vault: Never store secrets in application configuration files. Store them in Azure Key Vault and reference them using Key Vault References in App Services/Functions.
2. Compute (App Service, Functions, AKS)
- Azure Functions: For production serverless, use the Premium plan to avoid cold starts and gain VNet integration capabilities, unless strict cost minimization on the Consumption plan is required.
- AKS (Azure Kubernetes Service): Use Azure CNI for advanced networking. Enable Microsoft Entra ID integration for Kubernetes RBAC. Use Azure Policy to enforce pod security standards.
- App Service: Enable VNet Integration to access private resources. Turn on "Always On" (Basic tier and above) to prevent the worker process from idling out.
3. Data (Cosmos DB, Azure SQL, Storage)
- Cosmos DB: Carefully choose the Partition Key, as it determines scalability and performance. Changes to the partition key require data migration.
- Azure SQL Database: Enable Transparent Data Encryption (TDE). Use Private Endpoints (Azure Private Link) to ensure database traffic never traverses the public internet.
- Storage Accounts: Disable public network access on Storage Accounts. Use Shared Access Signatures (SAS) with short expiration times for temporary client access to blobs.
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.
- 2mo ago First seen · 39 lines · 68 tokens per session scan A 7718e2ce6499
azure is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 3mo ago), licensed MIT. It adds 68 tokens to every session and 609 once invoked, about $0.0003 per session on Opus 5.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…
cloudflare-artifacts-interface
Operate Cloudflare Artifacts, Cloudflare's Git-compatible versioned storage for agents, from an agent session through the REST API, Wrangler, a Worker binding, or plain git. Use when someone wants a repo per agent, session, task, or user; wants to create, fork, import, list, read, or delete Artifacts repos or…
async-event-agent
A guide to building agents that react to events instead of waiting for a user message each turn. Events can include email, webhooks, chat messages, timers, alerts, and interruptions during tool work.
skill-creator
Generate a new skill from a plain-language description — decides invocation control, arguments, and context cost, then scaffolds, validates, and tests it.
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.