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/gitcmurf/revrem/meminit-docopsnpx skills add GitCmurf/revrem --skill meminit-docopsgit clone --depth 1 https://github.com/GitCmurf/revremWhat 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.00071 | $0.03121 |
| Opus 5 | $0.00036 | $0.01561 |
| Sonnet 5 | $0.00014 | $0.00624 |
| Haiku 4.5 | $0.00007 | $0.00312 |
Grade A, and why
meminit-docops 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meminit DocOps Skill
Purpose
This skill teaches Codex how to use meminit to:
- retrofit Meminit into an existing repository (brownfield migration), and
- keep documentation compliant over time (local + CI gates).
It does not decide when your repo should adopt DocOps; that policy belongs in AGENTS.md and CI settings.
When to Use
Activate this skill when the user asks to:
- Retrofit Meminit into an existing repo (brownfield migration).
- Enforce DocOps compliance — check, fix, or audit governed documents.
- Create governed documents — e.g. ADRs, PRDs, specs, runbooks via
meminit new. - Troubleshoot documentation violations — diagnose and resolve
meminit checkfailures. - Set up CI gates or pre-commit hooks for DocOps enforcement.
- Resolve or look up document IDs using the Meminit index.
Safety rules (non-negotiable)
- Prefer read-only commands first:
scan,doctor,check. - Never run a write operation (
fix --no-dry-run,fix --plan <PLAN_PATH> --no-dry-run,migrate-ids --no-dry-run,migrate-ids --rewrite-references,protocol sync --no-dry-run, or any rename/rewrite) without:- showing a dry-run preview, and
- explicit user confirmation.
- Never attempt to “fix” semantic governance manually (ownership, approvals, status promotion) without asking.
- Do not introduce fake Markdown links like
[text](path)unless the target exists. - Prefer
--format jsonfor automation, treat STDOUT as machine output, and keep verbose reasoning on STDERR only. - For brownfield repos, prefer plan-driven changes (
scan --planthenfix --plan) over ad hoc write operations.
Quick command map
- Initialization:
meminit init - Repo readiness:
meminit doctor --format json - Repo discovery:
meminit context --format json(add--deepfor per-namespace document counts) - Compliance:
meminit check --format json(add--strictto promote warnings to errors) - Generate migration plan:
meminit scan --plan <PLAN_PATH> --format json - Safe preview:
meminit fix --dry-run --format json - Safe preview from plan:
meminit fix --plan <PLAN_PATH> --format json(add--namespace <NS>for monorepo safety) - Apply mechanical fixes:
meminit fix --no-dry-run --format json - Apply plan:
meminit fix --plan <PLAN_PATH> --no-dry-run --format json(add--namespace <NS>for monorepo safety) - Migration planning:
meminit scan --format json - Create governed doc:
meminit new <TYPE> <TITLE> --format json(key flags:--owner,--area,--description,--status,--keywords,--related-ids,--id,--dry-run,--namespace) - Type discovery:
meminit new --list-types --format json - ADR shortcut:
meminit adr new <TITLE> --format json - Migrate legacy IDs:
meminit migrate-ids --dry-run --format json(add--rewrite-referencesto update cross-refs) - Pre-commit hook:
meminit install-precommit --root . - Org profile helpers (optional):
meminit org status --format json,meminit org vendor --format json - Index + resolution:
meminit index --format jsonmeminit resolve <DOCUMENT_ID> --format jsonmeminit identify <PATH> --format jsonmeminit link <DOCUMENT_ID> --format json
- Protocol governance:
meminit protocol check --format json(drift detection for governed assets)meminit protocol sync --format json(preview-only by default; add--no-dry-runto apply)
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.
- yesterday First seen · 344 lines · 71 tokens per session scan A 6062611d4b9f
meminit-docops is a skill published in the GitHub repository GitCmurf/revrem (1 stars, last pushed 15d ago), licensed Apache-2.0. It adds 71 tokens to every session and 3,121 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
manage-skills
세션 변경사항을 분석하여 검증 스킬 누락을 탐지합니다. 기존 스킬을 동적으로 탐색하고, 새 스킬을 생성하거나 기존 스킬을 업데이트한 뒤 CLAUDE.md를 관리합니다.
release
Bump package.json version and create a git tag for npm release. Accepts semver bump type (patch/minor/major) or explicit version.
update-docs
오늘(또는 지정 날짜)의 git 커밋을 분석하여 docs/changelog/ 와 SETUP.md 문서를 자동 업데이트합니다. (CLAUDE.md는 기본 대상에서 제외).
update-wiki
오늘(또는 지정 날짜)의 git 커밋을 분석하여 GitHub Wiki(HyperAITeam/CLITrigger.wiki)를 업데이트합니다. 기존 페이지 뼈대는 유지하며 해당 섹션을 갱신하고, 완전히 새로운 기능이면 섹션/페이지를 추가합니다.
merge-worktree
Squash-merge the current worktree branch into the main branch (or a specified target). Analyzes git history and source code to craft a comprehensive commit message.
verify-implementation
프로젝트의 모든 verify 스킬을 순차 실행하여 통합 검증 보고서를 생성합니다. 기능 구현 후, PR 전, 코드 리뷰 시 사용.