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/monkey1wizard/golem-agents-legion/doc-syncnpx skills add monkey1wizard/Golem-Agents-Legion --skill doc-syncgit clone --depth 1 https://github.com/monkey1wizard/Golem-Agents-LegionWrote 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/monkey1wizard/golem-agents-legion/doc-sync)<a href="https://agentmods.dev/skills/monkey1wizard/golem-agents-legion/doc-sync"><img src="https://agentmods.dev/badge/skills/monkey1wizard/golem-agents-legion/doc-sync.svg" alt="Measured on agentmods" 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.00046 | $0.01513 |
| Opus 5 | $0.00023 | $0.00757 |
| Sonnet 5 | $0.00009 | $0.00303 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
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 today.
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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Sync Workflow
Use this skill to keep documentation structure aligned with code changes through the tracked NDJSON map in docs/structure/.
What This Skill Owns
- Read and update
docs/structure/structure-map.ndjsonone JSON record per line. - Validate records against
docs/structure/structure-map.schema.jsonwhen a validator is available. - Map file-level code changes to code-axis and doc-axis nodes.
- Keep untouched nodes unchanged; update only nodes re-verified in the current run.
- Render human-facing projections on demand without creating tracked projection files.
Core Inputs
docs/structure/structure-map.schema.jsondocs/structure/structure-map.ndjsontemplates/structure-map.template.ndjson- changed-file set from
git diff - affected docs under
docs/andREADME.md
Operating Rules
1. Drift Detection Baseline
- Always start from native
git diffplus direct file reads. - Treat graphify and codebase-memory-mcp as advisory-only enhancement lanes.
- If an advisory lane is unavailable, incomplete, or not ready, continue silently at file granularity.
2. NDJSON Update Discipline
- Keep one valid JSON object per line.
- Preserve stable key order inside each record.
- Preserve global line order sorted by
axis, thenid. - Replace only the lines for nodes actually affected by the current run.
- Do not rewrite untouched lines just to normalize formatting.
3. Node Model
- Code-axis nodes use
axis: "code"withkind: dir | module | file. - Doc-axis nodes use
axis: "doc"withkind: "doc-section". - Code axis detects undocumented code (
syncStatus: "missing"). - Doc axis detects stale or drifted narrative (
syncStatus: "drift"). - New nodes may start with
lastSyncedRef: nulluntil first verified sync.
4. Freshness Rules
- Only mark a node based on evidence gathered in the current run.
- Leave untouched nodes exactly as they were.
- For modified files, default conservatively to
syncStatus: "drift"until the affected docs are actually reviewed. - Never mass-flip nodes to
okbecause a run completed.
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.
- today First seen · 122 lines · 46 tokens per session scan A adc80cb38f46
doc-sync is a skill published in the GitHub repository monkey1wizard/Golem-Agents-Legion (15 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 1,513 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…