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-creatornpx skills add LuizEduPP/Rememb --skill skill-creatorgit clone --depth 1 https://github.com/LuizEduPP/RemembWhat 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.00035 | $0.00654 |
| Opus 5 | $0.00017 | $0.00327 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
skill-creator 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 2d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Creator
Create modular, self-contained packages that extend AI capabilities with specialized knowledge and workflows across different hosts.
Core Principles
Concise is Key
Challenge each piece: "Does the AI really need this?" Prefer concise examples over verbose explanations.
Progressive Disclosure
- Metadata (~100 words) - Always loaded
- SKILL.md body (<500 lines) - When triggered
- Bundled resources - As needed
Skill Structure
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter (name, description)
│ └── Markdown instructions
└── Bundled Resources (optional)
├── scripts/ - Executable code
├── references/ - Documentation
└── assets/ - Templates, icons
SKILL.md Format
---
name: my-skill
description: What it does AND when to use it (critical for triggering)
---
# Title
[Core instructions - imperative form]
## Sections as needed
Best Practices
| Do | Don't |
|---|---|
| Clear, comprehensive description | Vague one-liner |
| Imperative form ("Create", "Run") | Passive voice |
| Concise examples | Verbose explanations |
| Reference files for details | Everything in SKILL.md |
| Test scripts by running them | Assume they work |
| Use host-agnostic paths and wording | Hard-code one assistant's directory layout |
Portability Rules
- Write the skill in English unless a translated artifact is explicitly required
- Keep the main workflow independent from any single IDE, editor, CLI, or chat app
- Use placeholders such as
<skill-root>,<workspace>, and<output-dir>in examples - Put vendor-specific notes in a short compatibility section instead of the core flow
- Mention a specific assistant only when the skill itself is about that assistant
What NOT to Include
- README.md, CHANGELOG.md, INSTALLATION.md
- User-facing documentation
- Setup/testing procedures
Creation Process
- Understand - Get concrete usage examples
- Plan - Identify reusable scripts/references/assets
- Initialize - Create skill directory with SKILL.md
- Edit - Implement resources, write instructions
- Test - Verify with real usage
- Iterate - Refine based on feedback
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.
- 2d ago First seen · 99 lines · 35 tokens per session scan A 4d2a84d6ee5f
skill-creator is a skill published in the GitHub repository LuizEduPP/Rememb (4 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 654 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
agent-coordination
Find other agents, list participants in a conversation, send routed messages, attach files, and recover earlier conversation context (history / resolve a fuzzy reference / read a quoted message / read compressed summaries). Use whenever you need to delegate to another agent, address a peer in a multi-agent…
claim-agent-ownership
Orchestrator skill for resolving multi-daemon binding contention. Use when you (the orchestrator) detect an agent.binding.contested sync event indicating two daemons are racing for the same agent — explicitly rebind ownership to a chosen target daemon so subsequent dispatches route deterministically. Implements Gap…
human-approval
Request human approval before performing a SAFETY-CRITICAL, IRREVERSIBLE, or SCOPE-EXPANDING action — submit a structured context (action, scope, risk, consequence) plus options, then STOP the current turn. The platform redispatches the agent after the human decides. NEVER use for routine deliverables (writing docs /…
skill-authoring
Generate Prismer-compliant skill drafts from user intent, documentation URLs, existing code, or service endpoints. Use whenever the user says "make this a skill", "package this workflow", "create a skill for X", or wants to capture a repeatable workflow into a reusable artifact. Outputs a multi-file manifest (SKILL.md…
plugin-dev
Prismer Evolution Plugin 开发指南 — 快速迭代 hook/skill、调试、日志查看、测试、发布全流程.
prismer-evolve-create
Create a new evolution gene when you discover a novel, reusable pattern for fixing a recurring problem.