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/create-prs/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/create-prs)<a href="https://agentmods.dev/skills/fastrepl/anarlog/create-prs"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/create-prs/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/create-prs"><img src="https://agentmods.dev/badge/skills/fastrepl/anarlog/create-prs.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.00064 | $0.01012 |
| Opus 5.5 | $0.00026 | $0.00405 |
| Sonnet 5.5 | $0.00013 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
create-prs 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create missing GitButler PRs
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 create missing PRs for branches 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 stack-aware PR creation,
and the repository's preferred authenticated forge tools for reads. Derive the
repository, push remote, and target from the current workspace.
Invoking this workflow authorizes creating missing PRs and the in-scope pushes that creation requires. Creating this skill alone does not run that workflow. Do not merge PRs, enable auto-merge, or publish unrelated work.
Discover missing PRs
- Read
but status --jsonto map applied branches, their commits, existing review IDs, and dependencies from base to tip. Scope defaults to all applied branches; honor a narrower user selection. Exclude trunk, workspace/internal refs, empty branches, and branches already merged upstream. - Verify each branch against live forge state using the exact head repository and full head branch name. A cached review ID is only a lead. Include drafts as existing PRs and paginate results. Skip branches with an open matching PR. Investigate a closed/merged PR before treating the branch as new work; do not automatically reopen it or publish already-landed commits. Report ambiguous matches instead of guessing.
- Inspect each missing branch's complete changes relative to its intended PR
base with
but show/but diff, including all commits. For a stacked PR, describe that branch's contribution and dependency rather than repeating ancestors' changes. Preserve unrelated uncommitted changes; do not commit everything merely to publish PRs. - Check the actual push destinations with
but push <branch-name> --dry-runwhere publishing could include ancestors or unfamiliar tracking. Never push a feature branch into trunk. If creation would publish unrelated ancestor work or rewrite shared history without authorization, finish independent PRs and report the specific blocked branch. Keep hooks and push protections on.
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 · 84 lines · 64 tokens per session scan A 7a7e1c0b0157
create-prs is a skill published in the GitHub repository fastrepl/anarlog (9,621 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 1,012 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…