Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/agenturehq/agenture-loop/docs-syncnpx skills add AgentureHQ/agenture-loop --skill docs-syncgit clone --depth 1 https://github.com/AgentureHQ/agenture-loopWhat 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 | $0.00078 | $0.01287 |
| Opus 5 | $0.00039 | $0.00643 |
| Sonnet 5 | $0.00016 | $0.00257 |
| Haiku 4.5 | $0.00008 | $0.00129 |
Grade A, and why
docs-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 yesterday.
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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs sync (/agn:docs-sync)
Purpose
Every time a work unit closes (task → done, feature close, epic close), taskman.sh appends an entry to tasks/docs-sync-queue.txt and prints a "Doc-sync pending" hint. This skill processes that queue: it reviews upstream docs/* files for drift against each closed unit, proposes diffs, and clears the entry once the user approves.
Follow plugins/agn/rules/doc-maintenance.md for what to check and when no update is needed.
Arguments
| Position | Variable | Value |
|---|---|---|
$1 |
filter | Optional. Without an argument, process all pending entries. With a number, process only that line of the queue (1-indexed). With a slug or path, process only entries matching that id. |
Preconditions
tasks/docs-sync-queue.txtexists. If missing or empty, report "No pending doc-sync entries." and stop.- For each entry being processed, the named unit file must exist (closed task in
tasks/done/, feature intasks/features/, epic intasks/epics/).
Workflow
-
Read the queue — Load
tasks/docs-sync-queue.txt. Each line:<ISO-8601 timestamp> <kind> <id-or-path>kindistask,feature, orepic. For task,id-or-pathis the full path undertasks/done/. For feature/epic, it is the slug.Apply
$1filter if provided. -
For each entry, in order:
a. Load context. Read the closed unit's file. If it carries
feature: <slug>orepic: <slug>, also read the parent. If the closed unit links to a spec underdocs/<area>/.../-spec.md, read that spec.b. Check upstream docs in dependency order (per
rules/doc-maintenance.md):docs/vision.mddocs/spec.mddocs/requirements.mddocs/architecture.md- Linked spec under
docs/<area>/.../-spec.md(if applicable)
For each doc, ask:
- Does the doc state a behavior or intent that the closed work changed or invalidated?
- Does the doc lack a behavior or intent that the closed work now exhibits?
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.
- yesterday First seen · 89 lines · 78 tokens per session scan A d551c391104d
docs-sync is a skill published in the GitHub repository AgentureHQ/agenture-loop (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,287 once invoked, about $0.0004 per session on Opus 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
echo
Use when the user references past sessions, asks 'what did we do', 'do you remember', 'last session', 'recall', or 'continue from'.