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/mahmoudimus/simba/simba-codex-lifecyclenpx skills add mahmoudimus/simba --skill simba-codex-lifecyclegit clone --depth 1 https://github.com/mahmoudimus/simbaWrote 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/mahmoudimus/simba/simba-codex-lifecycle)<a href="https://agentmods.dev/skills/mahmoudimus/simba/simba-codex-lifecycle"><img src="https://agentmods.dev/badge/skills/mahmoudimus/simba/simba-codex-lifecycle.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 | $0.00070 | $0.00487 |
| Opus 5 | $0.00035 | $0.00244 |
| Sonnet 5 | $0.00014 | $0.00097 |
| Haiku 4.5 | $0.00007 | $0.00049 |
Grade A, and why
simba-codex-lifecycle 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
Simba Codex Lifecycle
Run this routine for implementation tasks in Simba-enabled repositories.
Required Sequence
- Recall relevant memory first (use the user request as query text):
simba codex-recall "<user request>"
- Run status once per session:
simba codex-status
Do not run this on every prompt. Re-run only if:
- there was a long pause or major context shift,
- memory actions fail unexpectedly,
- you are about to finalize and want a fresh check.
- Codex
PreCompactis the primary automatic session-analysis path. Ifcodex-statusstill reports a raw JSONL transcript aspending_extractionand you need to analyze it now, run the explicit storage path:
simba codex-extract --run
If that reports no candidates or fails, run the manual prompt path:
simba codex-extract
- Before final handoff, run finalize:
simba codex-finalize
Finalize Inputs
Prefer to include both response text and transcript path when available:
simba codex-finalize --response-file /path/to/response.txt --transcript /path/to/transcript.jsonl
If those files are not available, still run simba codex-finalize as a best-effort check.
If simba is not in PATH, use:
uvx --from /Users/mahmoud/src/ai/simba simba codex-status
Output Discipline
- Mention whether
codex-recallreturned relevant memories and how they informed your approach. - Mention in your final update that lifecycle checks were run.
- If you run
codex-extract --run, mention the stored / duplicate / error counts. If extraction remains pending, runcodex-extractand report that action.
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.
- 3d ago First seen · 72 lines · 70 tokens per session scan A 33dead9b6876
simba-codex-lifecycle is a skill published in the GitHub repository mahmoudimus/simba (6 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 487 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
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
ix
This skill should be used when answering structural questions about a codebase: understanding what a symbol is, tracing flows, measuring change impact, finding callers/callees/imports, or detecting code smells. It drives the Ix CLI (ix map/explain/trace/impact/search/rank/smells) against a persistent code graph stored…
services-audit-cron
Use when scheduling the canonical biweekly services-audit cron loop for Empirica's AI service scanner (Phase 3). The auditor body is empirica services-audit — captures a fresh scan, diffs against the previous, and emits a notification when novel running services appear. This skill provides the prompt template that…
message-cleanup
Daily housekeeping body for the canonical message-cleanup loop. Prunes expired git-notes mesh messages so the inbox stays focused on un-read ones. Loaded by the loop scheduler when the cron entry fires (default 03:17 daily) — never invoked directly by a user. Triggers: from the message-cleanup loop, "message…