anarlog is a local-first AI meeting notetaker that captures device audio, transcribes meetings, and stores notes, transcripts, and recordings on the user's computer. It is for people who want meeting notes without adding a bot to calls or sending conversation data to an external cloud. The catalogue entries provide agent integrations and workflows for the application.
Borrowing it
Nothing to install: this file belongs to fastrepl/anarlog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fastrepl/anarlog/main/.agents/skills/release-cli/SKILL.mdgit clone --depth 1 https://github.com/fastrepl/anarlogWrote 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/fastrepl/anarlog/release-cli)<a href="https://agentmods.dev/skills/fastrepl/anarlog/release-cli"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/release-cli/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fastrepl/anarlog/release-cli"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/release-cli.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.00498 |
| Opus 5.5 | $0.00012 | $0.00199 |
| Sonnet 5.5 | $0.00006 | $0.00100 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
release-cli 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 1mo 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
Release CLI
Review every release. Inherit scope and session authorization from Release a New Version.
- Compare user-visible product changes with
apps/cli,crates/agent-access, help and CLI contract snapshots. Check commands, flags, JSON fields/errors, pagination, local/cloud selection, output/exit codes, and supported formats. Implement required parity before candidate freeze; document intentional capability differences, reuse reasons, and explicit deferrals. - Follow
cli_ci.yamland rootAGENTS.md: run affected locked tests, Clippy with the workflow flags, release CLI build, isolated smoke tests, and docs/skill validation. Preserve Linux and Windows verification; a local macOS executable does not establish other platforms' results. Coordinate public examples with Release Docs. - Complete the shared Agent packages review once with Release MCP. The authored skill, generated mirrors, public documentation, and installed plugin are separate publication states.
- Verify the CLI extracted from each final signed desktop artifact. Confirm
APP_VERSIONreached the build and packaged--versionmatches the requested desktop release. Runscripts/verify-packaged-cli.py <package-root> <version>as used in the platform workflow, plus affected command checks against isolated fixtures. Reuse its MCP results with Release MCP. A developer binary onPATH, a staging package, or unit tests alone cannot verify the final stable package. - Check help, loading/runtime dependencies, output/exit codes and shutdown. After
upgrade, verify the supported CLI installer resolves the new bundled binary;
consult
skills/anarlog/references/setup.mdand the current installer. Never use user data as a disposable fixture or copy/reset databases and sync identity.
Return parity decisions, source and artifact versions/hashes, checks, supported install/update evidence, and unavailable platforms or pending work. A mobile-only release does not authorize publishing an unrelated desktop CLI.
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.
- 1mo ago First seen · 40 lines · 31 tokens per session scan A f43dd7027053
release-cli is a skill published in the GitHub repository fastrepl/anarlog (9,621 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 498 once invoked, about $0.0001 per session on Opus 5.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-09-21.
Other skills, from other repositories
deployment-rules
Release/deployment standards — semantic-release, commitlint, version sync, the updater. Load for /prepare-release and changes to release.config.mjs / commitlint / workflows / version files. Owned by project-steward.
app-release
Use when the user asks to release a new version, ship a build, or publish a Skill Zoo release. Also use when a tag push results in Homebrew 404 errors or missing artifact failures.
npm-release
Use when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli. Also use when npm publish fails because of duplicate versions, npm authentication, browser authentication, dist-tag propagation, tarball contents, bin entry issues, or…
coding-standards
General repo rules enforced by ESLint/TypeScript/CI — PRs-only, never bypass lint, import ordering, type imports, path privacy, commit format. Load for any code change.
deployment-procedures
Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.