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/sweep-workspace/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/sweep-workspace)<a href="https://agentmods.dev/skills/fastrepl/anarlog/sweep-workspace"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/sweep-workspace/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/sweep-workspace"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/sweep-workspace.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.00063 | $0.01667 |
| Opus 5.5 | $0.00025 | $0.00667 |
| Sonnet 5.5 | $0.00013 | $0.00333 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
sweep-workspace 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 27d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sweep GitButler workspace
Applicability
Use only in the Anarlog repository or its checkouts/worktrees when the active
checkout branch is exactly gitbutler/workspace. Before running this workflow,
check with git symbolic-ref --quiet --short HEAD (a read-only branch check).
On any other branch or detached HEAD, skip this skill and use the normal Git
workflow. Do not initialize GitButler or switch branches to activate the skill.
Use this checkout's skills, not a global copy or another checkout's skills.
Use this skill when asked to sweep PRs in the Anarlog GitButler workspace.
Read the repository-local but skill and the active repository's AGENTS.md and workflow
skill when present. Use but for version control and the repository's preferred
authenticated forge tools for PR operations. Derive the repository and configured
target from the current workspace.
This skill coordinates the three focused workflows. Read the repository-local skill when its stage begins: create-prs, fix-prs, and update-prs. Do not automatically spawn subagents or run stages concurrently.
A sweep invocation authorizes in-scope PR creation, pushes, necessary history rewrites, workspace updates, conflict repairs, review replies/resolutions, metadata edits, and ready non-draft merges. Preserve unrelated work and active collaborators' edits. Editing this skill does not execute a sweep.
1. Merge PRs that are already ready
- Inspect
but status --jsonand map applied branches to live open PRs by exact head repository/branch. Record bases, remote SHAs and stack dependencies. Honor a narrower user scope; skip missing, closed or merged PRs in this stage. - Inspect current published code, all paginated reviews/threads/conversation findings and current checks. Merge only non-drafts with passing applicable required checks, satisfied review requirements, no conflicts, and no remaining actionable or unverified findings. Include outdated unresolved findings and linked reviewer reports; incomplete access/coverage blocks readiness.
- Do not fix code, publish local changes or create PRs to make this initial queue ready. An unpublished fix does not clear a finding on the remote head. A fix in an upper PR qualifies only when that verified fix is included in the same ready merge prefix; an earlier prefix without it is not safe.
- Merge nearest trunk first, in batches of at most 10 PRs total. Prerequisites must already be merged or included in the same supported stack merge. Skip blocked ancestors and their descendants; continue independent ready stacks.
- Immediately before each request, recheck every included PR's head, base, draft state, checks, reviews and mergeability. Use the repository's merge method and the reviewed SHA; changed heads invalidate readiness.
- Prefer a supported GitButler PR merge operation with head protection. Otherwise
use authenticated forge tools: ordinary GitHub PRs support
gh pr merge <PR> --match-head-commit <SHA>with the repo's merge method. Native GitHub stacks need the supported asynchronous stack merge API; verify its current request fields and head guard rather than guessing or falling back to a legacy merge. Neitherbut landnor enabling auto-merge substitutes for this stage. - Confirm each requested merge through live terminal PR/operation state before advancing dependent PRs or cleaning up branches. Re-read affected descendants after each confirmed merge. Async acceptance is not merge completion; retain pending operation IDs for continuation and do not mutate affected stacks while their merge is pending.
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.
- 27d ago First seen · 133 lines · 63 tokens per session scan A 8903a56d0a44
sweep-workspace is a skill published in the GitHub repository fastrepl/anarlog (9,621 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,667 once invoked, about $0.0003 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-10-02.
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.
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.
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.
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.
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…