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/utundry/sloplesscode/remembernpx skills add Utundry/sloplesscode --skill remembergit clone --depth 1 https://github.com/Utundry/sloplesscodeWhat 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.00060 | $0.00611 |
| Opus 5 | $0.00030 | $0.00305 |
| Sonnet 5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
remember 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 yesterday.
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.
What it actually says
Remember — Save to Super Memory
Save the provided information to the local semantic memory store.
Arguments
$ARGUMENTS
Instructions
-
Parse the arguments to extract:
- content: The main text to remember (required — everything before any flags)
- agent: Agent/user ID (flag
--agent <id>, default:"default") - type: Memory type (flag
--type <type>, default:"fact")fact— factual informationpreference— user preferences and habitsexperience— things that happenedtask— tasks and todoscontext— project/session context
- importance: Float 0.0–1.0 (flag
--importance <n>, default:0.7) - tags: Optional comma-separated tags (flag
--tags <t1,t2>)
-
If no flags are provided, treat the entire argument as content and use smart defaults:
- Detect memory type from content: preferences →
preference, tasks/todos →task, etc. - Set importance based on urgency words ("important", "critical", "always") → 0.9+
- Detect memory type from content: preferences →
-
Call
mcp__super-memory__memory_storewith the parsed values. -
Confirm success with the returned memory ID and a short summary.
Examples
/remember User prefers Python over JavaScript
/remember --agent project1 --type preference --importance 0.9 Always use async/await, never callbacks
/remember --type task --importance 0.8 Review PR #42 before Friday
/remember --type context --tags docker,infra The production DB runs on port 5433 not 5432
Output format
After saving, respond with:
Saved to memory: "<first 60 chars of content>"
ID: <uuid>
Type: <type> | Importance: <score>
If the memory server is unreachable, say so clearly and suggest running:
docker compose up qdrant -d and uvicorn app.main:app in D:\work\mnemoforge
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.
- yesterday First seen · 58 lines · 60 tokens per session scan A 2d4336066070
remember is a skill published in the GitHub repository Utundry/sloplesscode (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 611 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-31.
Other skills, from other repositories
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
critique
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks…
github-dashboard
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.
audio-jingle
Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.
dating-web
A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social…