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/jtsang4/efficient-coding/memosnpx skills add jtsang4/efficient-coding --skill memosgit clone --depth 1 https://github.com/jtsang4/efficient-codingWhat 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.00073 | $0.01768 |
| Opus 5 | $0.00036 | $0.00884 |
| Sonnet 5 | $0.00015 | $0.00354 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
memos 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.
How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memos API Skill
This skill combines two layers:
- low-level API access for exact Memos endpoints
- task-oriented query helpers for common memo retrieval jobs
- tag inventory helpers so the calling agent can inspect existing hashtags before deciding whether to reuse them
Scope is intentionally limited to:
- attachment operations
- memo operations
- activity operations
It does not cover user management, auth setup beyond the local .env, shortcuts, identity providers, or instance settings. If the request drifts there, say the skill scope is limited instead of guessing unsupported commands.
What this skill provides
- A Bun CLI at
scripts/memos.ts - Endpoint discovery and direct API calling via
ops,describe, andcall - Task-oriented memo helpers via
latest,recent, andsearch - A
list-tagshelper that aggregates existing tags, counts, recency, and sample memo snippets - A file-to-attachment helper so agents do not have to hand-roll base64 payloads
- A compact operation catalog at
references/api-summary.md - Query recipes and time-window guidance at
references/query-recipes.md
Setup
- Work from the skill directory.
- Ensure
.envcontains:MEMOS_BASE_URLMEMOS_ACCESS_TOKEN
- Verify config:
bun run scripts/memos.ts config
MEMOS_BASE_URL may be either the instance root such as http://localhost:5230 or the API base such as http://localhost:5230/api/v1. The CLI normalizes both.
Choose the right path
Use the high-level commands first when the user asked for a retrieval task, not a specific endpoint.
- Latest memo or latest N memos:
bun run scripts/memos.ts latest --count 5
- Recent memos inside a time window:
bun run scripts/memos.ts recent --days 7 --window rolling --include-content
- Search by text or tag:
bun run scripts/memos.ts search --text agent --tag Thought --days 30
- Inspect existing tags before deciding which hashtags to reuse in a new memo:
What ships with it
7 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.
- yesterday First seen · 220 lines · 73 tokens per session scan A 9135d448a6ab
memos is a skill published in the GitHub repository jtsang4/efficient-coding (2 stars, last pushed 6d ago), licensed MIT. It adds 73 tokens to every session and 1,768 once invoked, about $0.0004 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
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
interview
Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
test
Detect the project’s test stack, run the narrowest useful tests, create tests when authorized, and report coverage/gaps honestly.
verify
Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…