Borrowing it
Nothing to install: this file belongs to OctopusGarage/alcove. 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/OctopusGarage/alcove/main/.agents/skills/alcove-doc-sync/SKILL.mdgit clone --depth 1 https://github.com/OctopusGarage/alcoveWrote 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/octopusgarage/alcove/alcove-doc-sync)<a href="https://agentmods.dev/skills/octopusgarage/alcove/alcove-doc-sync"><img src="https://agentmods.dev/badge/skills/octopusgarage/alcove/alcove-doc-sync/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/octopusgarage/alcove/alcove-doc-sync"><img src="https://agentmods.dev/badge/skills/octopusgarage/alcove/alcove-doc-sync.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.00050 | $0.00754 |
| Opus 5.5 | $0.00020 | $0.00302 |
| Sonnet 5.5 | $0.00010 | $0.00151 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
alcove-doc-sync 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alcove Doc Sync
Use this workflow to keep Alcove implementation and documentation aligned.
Procedure
- Inspect the current diff:
git diff --name-only HEAD
git diff --cached --name-only
git ls-files --others --exclude-standard
- Map changed behavior to documentation:
README.md: short install and core usage only.docs/architecture.md: global relationships between managed knowledge bases, external knowledge, memory modules, automations, dashboard, and agent entries.docs/modules.md: module contracts, storage shape, and generated indexes.docs/entry-modes.md: Hub, KB workspace, MCP, Codex, and Claude behavior.docs/data-and-backup.md: user data paths, exports, backup, and sync.docs/usage.md: commands and operator flows.docs/radars.md: radar presets, source adapters, reporting, and notifications.docs/okf-profile.md: OKF conventions, catalogs, and indexes.docs/evals/agent-quality-gates.md: hooks, smoke, AI eval, and gate rules.site/index.html: public GitHub Pages overview. Always review it when public docs, entry modes, workspaces, MCP/CLI routing, dashboard, publishing, install, or module boundaries change. Update it only when the global public story would drift: positioning, entry model, installation path, or top-level module relationships. Keep detailed feature flows indocs/, not on the public landing page.
- Run the entry-mode impact checklist for every user-facing feature:
- Hub workspace: should
src/alcove/profile_templates/hub/skills/alcove-hub/SKILL.mdandsrc/alcove/profile_packs.pygain or change intent routing, protocol steps, or safety rules? The Hub is the default day-to-day user entry. - Business workspace: should
src/alcove/profile_templates/workspace/skills/alcove-workspace/SKILL.mdor generated workspace guidance change for scene-scoped family/work/travel behavior? - Managed KB workspace: should KB skills, inbox/capture commands, or OKF workflows change?
- Global MCP: should this remain a lightweight MCP operation, become a command
hint, or be exposed only in
full/KB toolsets? - CLI: does the command shape still match how Hub and MCP agents should call it?
- Service/dashboard/publishing: does background, browser, publishing, or public Pages behavior need docs, a site overview review, smoke, or AI eval updates?
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 · 76 lines · 50 tokens per session scan A 013c560e105b
alcove-doc-sync is a skill published in the GitHub repository OctopusGarage/alcove (0 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 754 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
siyuan-plugin-development
Official frontend plugin development workflow. After the user explicitly opts in, clarify missing requirements, confirm a short plan, implement in a managed copy, verify, and package. Installation and activation require separate authorization.
starcat-ui-prototype
A design skill for creating macOS interface prototypes and visual designs for Starcat, a GitHub star-management and AI knowledge-organising app. It follows Apple’s Liquid Glass design language for macOS 26.
starcat-update-changelog
Update Starcat changelog documents in supports/starcat-pro/ by reading ALL git commits from the main Starcat project and generating categorized release notes in both English and Chinese. Use this skill whenever the user wants to update changelog, release notes, update records, or sync the changelog with recent…
starcat-release
A project-specific procedure for releasing the Starcat macOS app through its App Store and direct-download channels.
github-issue-lifecycle
A GitHub Issue workflow for taking a code change from request to review, approval, testing, and closure. It can also keep a GitHub Project board—the task board attached to a repository—in sync.
starcat-localization-sync
A process for managing Starcat’s app translations from draft text through review, import, and release across 18 languages. It keeps the app’s translation catalogue and the public translation repository aligned.