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 commands/gengzezhou/memex/pushgit clone --depth 1 https://github.com/GengzeZhou/memexWhat 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.00008 | $0.00191 |
| Opus 5 | $0.00004 | $0.00096 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
push 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 3d 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.
What it actually says
Workspace Configuration
!cat workspaces.yaml
What to Push
The user wants to push content to: $ARGUMENTS
Rules:
- Check
workspaces.yamlto confirm the target workspace exists and allows writes - Only push to directories listed under
operations.writefor that workspace - Never overwrite existing files without asking — create new files or append
- After pushing, note what was pushed
Common push operations:
- deadlines → workspace: Sync
schedule/deadlines.mdto a workspace's task directory - idea → workspace: Move a research idea from session notes into a workspace's ideas folder
- summary → workspace: Push a session summary to a relevant project directory
Execute the push and confirm what was written.
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.
- 3d ago First seen · 26 lines · 8 tokens per session scan A cc08f836d6de
push is a command published in the GitHub repository GengzeZhou/memex (10 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 191 once invoked, about $0.0000 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
version
Show installed vs latest ai-sdlc plugin version. Bypasses the 24h SessionStart cache.
thread
Manage conversation threads (create, switch, update, delete, show).
handoff
Generate or load a session handoff. Usage: /handoff [create|resume].