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 awsgit 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/aws)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/aws"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/aws/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/aws"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/aws.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.00072 | $0.00673 |
| Opus 5.5 | $0.00029 | $0.00269 |
| Sonnet 5.5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
aws 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 1mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon Web Services (AWS) Best Practices
STOP. Your knowledge of AWS may be outdated. Prefer retrieval over pre-training for any version-sensitive AWS configuration. Fetch current documentation when in doubt.
Production-grade standards for designing, deploying, and managing infrastructure on AWS.
1. Security & IAM (Identity and Access Management)
- Principle of Least Privilege (PoLP): Never use
*(wildcard) actions or resources in IAM policies unless absolutely required (e.g., specific S3 list actions). Scope policies to specific ARNs and exact actions. - Root Account: Never use the root account for day-to-day operations. Use AWS SSO (IAM Identity Center) or assume roles.
- Secrets Management: Never hardcode secrets in code or environment variables attached to instances. Always use AWS Secrets Manager or AWS Systems Manager Parameter Store (SSM).
2. Serverless (Lambda & API Gateway)
- Cold Starts: Minimize cold starts in Lambda by keeping deployment packages small. For Node.js/TypeScript, use tools like
esbuildto bundle and tree-shake code. - Concurrency: Set reserved concurrency for critical functions to ensure they always have execution capacity.
- Idempotency: Lambda functions should be idempotent, especially when triggered by SQS, SNS, or EventBridge, as AWS guarantees at-least-once delivery (not exactly-once).
3. Storage & Databases (S3, DynamoDB, RDS)
- S3 Security: ALWAYS enable "Block Public Access" at the bucket level unless serving a static website. Enforce server-side encryption (
AES256oraws:kms). - DynamoDB: Prefer single-table design when access patterns are strictly known. Use On-Demand capacity for unpredictable workloads and Provisioned capacity (with Auto Scaling) for predictable workloads to save costs.
- RDS: Never place RDS instances in public subnets. They must reside in private subnets, accessed via Bastion Hosts, VPN, or Session Manager.
4. Networking (VPC)
- Multi-AZ: Always deploy critical resources (NAT Gateways, RDS, ALB, ECS) across at least two Availability Zones for high availability.
- Security Groups: Security Groups are stateful. Only allow necessary inbound ports (e.g., 443 for HTTPS). Do not open
0.0.0.0/0on port 22 or 3306.
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.
- 1mo ago First seen · 40 lines · 72 tokens per session scan A 45cdf08282c3
aws is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 673 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…
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.
context-update
Save a brief mid-session checkpoint to this workspace and update current state only when a priority or open thread changed. Use only when the user explicitly asks to checkpoint or save current progress.