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 skills/luizedupp/rememb/skill-writernpx skills add LuizEduPP/Rememb --skill skill-writergit clone --depth 1 https://github.com/LuizEduPP/RemembWrote 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/luizedupp/rememb/skill-writer)<a href="https://agentmods.dev/skills/luizedupp/rememb/skill-writer"><img src="https://agentmods.dev/badge/skills/luizedupp/rememb/skill-writer.svg" alt="Measured on agentmods" 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 | $0.00047 | $0.01349 |
| Opus 5 | $0.00023 | $0.00674 |
| Sonnet 5 | $0.00009 | $0.00270 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
skill-writer 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Writer
Overview
Use this skill to create or refactor skills that stay focused, portable, and easy to discover. The primary workflow should work across assistants, IDEs, CLIs, and chat applications without assuming a specific host.
When to Use
Use this skill when:
- Creating a new skill from scratch
- Updating or redesigning an existing
SKILL.md - Fixing frontmatter, structure, or discovery quality
- Converting a prompt or workflow into a reusable skill
- Making an existing skill more host-agnostic
Core Workflow
1. Define the skill boundary
First determine the exact capability the skill should provide.
- What outcome should the skill produce?
- When should the skill activate?
- What inputs, files, or tools does it rely on?
- Which parts are universal, and which are host-specific?
Keep the scope narrow. One skill should solve one coherent problem.
2. Choose the skill root
Pick a concrete <skill-root> that matches the current environment. The skill itself should not assume whether that root is user-level, workspace-level, registry-managed, or tool-managed.
Install the skill under:
<skill-root>/skill-name/
If the environment supports multiple installation scopes, choose the scope that matches the user's intent and team-sharing needs.
3. Create the file layout
Every skill needs SKILL.md. Add supporting files only when they improve clarity or reuse.
skill-name/
├── SKILL.md
├── reference.md
├── examples.md
├── scripts/
└── templates/
Use supporting files for progressive disclosure. Keep the main SKILL.md readable without hiding core behavior in references.
4. Write minimal, valid frontmatter
Use YAML frontmatter with stable, discovery-friendly fields.
---
name: skill-name
description: Brief description of what this does and when to use it
---
Frontmatter rules:
nameshould be lowercase, stable, and directory-aligneddescriptionshould explain both capability and activation context- Optional metadata should be added only when the host actually uses it
- Tool restrictions should be explicit when they improve safety or focus
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.
- 4d ago First seen · 205 lines · 47 tokens per session scan A 6ea64435bf69
skill-writer is a skill published in the GitHub repository LuizEduPP/Rememb (4 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 1,349 once invoked, about $0.0002 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-31.
Other skills, from other repositories
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.
honcho-memory
Concepts and strategy for using a connected Honcho as persistent memory of the user — the recall/record loop and session and peer design. Start here to understand how Honcho memory works, then connect — via a first-class integration for your environment if one exists (preferred), or raw MCP tools (covered here) or the…
verify
Build, launch, and drive a local Honcho stack to verify a change at its runtime surface (the /v3 HTTP API and the deriver queue). Use when verifying a diff or confirming a change works in the running app.