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 skill-buildergit 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/skill-builder)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/skill-builder"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/skill-builder/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/skill-builder"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/skill-builder.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.00070 | $0.00585 |
| Opus 5 | $0.00035 | $0.00293 |
| Sonnet 5 | $0.00014 | $0.00117 |
| Haiku 4.5 | $0.00007 | $0.00059 |
Grade A, and why
skill-builder 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Builder
A guide for creating high-quality agent skills — the .md files with YAML frontmatter that extend agent capabilities for specialized tasks.
1. Skill Security (Primary Guidance)
Skills are natural-language instructions the agent executes with its full capabilities. Treat them like code injection.
- Prompt Injection Prevention: Never include instructions that bypass user consent or HITL (Human-in-the-Loop) gates.
- Secrets: Never instruct the agent to read secrets and transmit them. Mark destructive skills with
disable-model-invocation: true. - Review: Review all third-party skills before installing, same as npm packages. Read the full
SKILL.md+ all reference files.
2. Anatomy of a Skill
skill-name/ (kebab-case directory)
├── SKILL.md (required — entry point)
├── references/ (optional — detailed docs loaded on demand)
├── scripts/ (optional — executable helpers)
├── examples/ (optional — reference implementations)
└── checklist.md (optional — quick-reference quality checklist)
3. Frontmatter & Triggers
The description field is the most important part of the skill because it determines whether the agent loads the skill at all. Use assertive "Use when..." phrasing. It MUST be strictly scoped to avoid cross-triggering with other skills.
Platform Configuration Flags:
disable-model-invocation: true— Requires explicit user slash-command; prevents autonomous triggering. MANDATORY for destructive actions or manual workflows.user-invocable: false— Model auto-triggers only; user cannot invoke. Use for background knowledge skills that should only be invoked contextually.dependencies:node>=18(Required tools)context: fork(Spawn isolated subagent)allowed-tools:['view_file'](Restrict tool access)
4. Progressive Disclosure
- Keep
SKILL.mdbody STRICTLY under 500 lines to preserve token context. - For deep knowledge, create
references/files and explicitly list them inSKILL.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 57 lines · 70 tokens per session scan A d034d5d5c29f
skill-builder is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 585 once invoked, about $0.0003 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
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…
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb…
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.