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 skills add memi-design/design-skills --skill codex-opsgit clone --depth 1 https://github.com/memi-design/design-skillsWrote 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/memi-design/design-skills/codex-ops)<a href="https://agentmods.dev/skills/memi-design/design-skills/codex-ops"><img src="https://agentmods.dev/badge/skills/memi-design/design-skills/codex-ops.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.1 | $0.00033 | $0.00680 |
| Opus 5 | $0.00016 | $0.00340 |
| Sonnet 5 | $0.00007 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
codex-ops 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 7d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Ops
Use this when Codex or Claude is operating inside the Memoire repository and needs a stable workflow for safe autonomous changes.
Core Rule
Prefer machine-readable command output whenever Memoire exposes it. Do not scrape terminal prose if a JSON surface exists.
Current JSON-first commands:
memi status --jsonmemi connect --jsonmemi notes list --jsonmemi notes info <name> --jsonmemi compose "..." --jsonmemi doctor --jsonmemi generate --jsonmemi export --json
Execution Pattern
- Inspect state first with JSON-capable commands.
- Use dry-run modes before mutating files when available.
- Make one coherent change at a time.
- Verify with focused tests or typecheck.
- Commit and push each lane separately.
Commit Hygiene
- Keep each commit scoped to one behavior or one workflow lane.
- Do not mix note content, command changes, and unrelated generated output.
- If the worktree is already dirty, treat existing changes as user state unless you know they were produced by your own current lane.
- Do not rewrite or revert unrelated files to make your diff cleaner.
Review Loop
- Read the diff before every commit.
- Prefer targeted regression tests over broad reruns first.
- If a command has a
--jsonmode, add or update tests against the structured payload rather than asserting on human-readable formatting. - When a fix changes behavior, verify both the focused path and the combined command suite that overlaps it.
Memory Capture
- If a workflow becomes stable, encode it in a built-in note or skill instead of repeating it in freeform prompts.
- If a command repeatedly needs structured output, add
--jsoninstead of teaching agents to parse ASCII tables or prose. - If a repository convention matters across many commits, capture it in a note, not only in one changelog entry or one conversation.
Safe Autonomy
- Prefer additive or explicitly scoped changes.
- Use
--dry-run,doctor, andstatus --jsonbefore destructive or broad operations. - Treat
.memoire/, generated outputs, preview artifacts, and user specs as project state, not disposable scratch space. - When a lane is already pushed to
main, reconcile local work toHEADinstead of silently diverging.
What ships with it
1 file 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.
- 7d ago First seen · 91 lines · 33 tokens per session scan A e846f5522477
codex-ops is a skill published in the GitHub repository memi-design/design-skills (7 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 680 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
ax-extract-workflow
Reconstruct workflow behind a past coding-agent artifact using local ax sessions/commits/skills/tool traces. Use when asked how X was built.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
commit-push-pr
Commit current changes, push to remote, and create or update a pull request. Use when the user wants to commit and create a PR, push changes and open a pull request, or ship their current work as a PR.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
memstack-security-git-guard
Use when the user says 'git-guard', 'check git protection', 'is this repo protected', 'verify gitleaks', 'set up git hooks', 'install git-guard', or wants to confirm a repo blocks secrets and internal files before commit. This is an installer and verifier, NOT a scanner (gitleaks does the actual scanning). Do NOT use…