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-telemetry/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-telemetry)<a href="https://agentmods.dev/skills/fastrepl/anarlog/release-telemetry"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/release-telemetry/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-telemetry"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/release-telemetry.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.00032 | $0.00678 |
| Opus 5.5 | $0.00013 | $0.00271 |
| Sonnet 5.5 | $0.00006 | $0.00136 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
release-telemetry 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Telemetry
Review every release; implement and verify affected paths and known gaps. Inherit scope and session authorization from Release a New Version. Do not turn a release review into an unrelated telemetry migration.
Implementation map
- Desktop product events:
apps/desktop/src/analytics.ts,plugins/analytics/, andcrates/analytics/. - Desktop errors and consent:
apps/desktop/src-tauri/src/lib.rs,plugins/tracing/, and current privacy/settings wiring. - Website:
apps/web/src/providers/posthog.tsx, analytics/privacy helpers underapps/web/src/lib/, andapps/web/src/telemetry.tsfor browser tracing. - Hosted services:
apps/api/src/main.rs, affected API/proxy instrumentation, andapps/stripe/when billing changes. - Requested mobile releases:
apps/mobile/src/lib/analytics.tsand the current mobile error-reporting/bootstrap path. Do not infer desktop coverage applies. - Native symbols and web source maps:
desktop_cd.yaml,web_cd.yaml, and their actions. Inspect the actual platform steps and destinations before checking uploads.
Review and verification
- Trace changed journeys through event/error production, consent/channel gates, sanitization, transport, and destination. Cover success, failure, cancellation, retries, and recovery where affected. Reuse existing instrumentation with evidence; implement required missing coverage before candidate freeze or record an explicit deferral and impact.
- Keep product analytics consent separate from crash-reporting consent. Preserve opt-out, private-route/global-privacy gates, redaction, deduplication, and bounded asynchronous delivery. Never include note/transcript content, credentials, keys, or raw private identifiers as diagnostic fixtures. Telemetry failure must not block recording, saving, or recovery.
- Run affected component tests using current CI commands, including opt-out,
sanitization, retry and collector-failure cases. Verify
APP_VERSION, channel, environment and serving revision reach events from the actual packaged or deployed runtime. Developer SDK initialization is not shipped evidence. - Verify affected PostHog ingestion and Sentry ingestion/symbolication against the shipped release and each deployed service revision. Use existing authorized test accounts and harmless synthetic diagnostics where supported; do not crash the user's working app or change their consent to obtain evidence. For disabled channels, verify no emission. Inspect matching native debug IDs/source maps; upload success alone does not prove a captured stack is symbolicated.
- Keep mocks, successful transport, destination ingestion, and symbolication as distinct evidence. Empty queries do not prove no events occurred. If credentials or suitable runtime evidence are unavailable, report that specific unchecked result; do not claim success or silently add a new release dispatch.
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 · 58 lines · 32 tokens per session scan A bbb9cd2e6baa
release-telemetry is a skill published in the GitHub repository fastrepl/anarlog (9,621 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 678 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
graphify-windows
Turn any folder of files into a navigable knowledge graph with community detection, an honest audit trail, and three outputs: interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPHREPORT.md.
lessons
How to propose and query distilled lessons (the experiential memory). Only project-steward persists; every other agent proposes/queries. Use when you discover a durable lesson or need prior experience for the current task.
webgl-standards
DORMANT (ADR-0017, 2026-07-20) - the TERMINAL VELOCITY scroll-film was retired and apps/landing is a static site with no GL surface; this skill is preserved for any future WebGL rebuild (conventions, verified version pins, playhead/scroll-rig/VAT/Gerstner/post-chain patterns, budgets, gate + semantic-layer machinery).…
agent-cli-standards
Agent-facing CLI standards — the argv-sentinel binary mode, the thin-client-over-the-bridge rule, allowlist projections, prompt-fencing third-party text, the stable machine-readable output contract, exit codes, throttling, and destructive-command operability. Load for changes under extensionbridge/agentcli.rs…
webgl-gate-audit
Procedures for auditing apps/landing TERMINAL VELOCITY WebGL phase gates - driving the browser to exact playhead positions across the 9 scenes, screenshot discipline, scrub + VAT determinism (scrub down THEN rewind to the same playhead -> identical frame), FPS sampling at the risk scenes, draw-call + bundle-size…
extension-standards
Browser-extension + bridge standards — MV3 (Chrome + Firefox), least-privilege permissions, the loopback pairing-token auth model, the shared TS↔Rust wire protocol, and the Chrome Web Store + Firefox AMO store-policy + pre-submission checklist. Load for changes under apps/extension/, extensionbridge/, and the…