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 skills add Lolaplex/agents-docs --skill docs-syncgit clone --depth 1 https://github.com/Lolaplex/agents-docsWrote 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/lolaplex/agents-docs/docs-sync)<a href="https://agentmods.dev/skills/lolaplex/agents-docs/docs-sync"><img src="https://agentmods.dev/badge/skills/lolaplex/agents-docs/docs-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/lolaplex/agents-docs/docs-sync"><img src="https://agentmods.dev/badge/skills/lolaplex/agents-docs/docs-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.00024 | $0.00219 |
| Opus 5.5 | $0.00010 | $0.00088 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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 20d 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.
What it actually says
Docs Sync Skill
Use this skill when a project needs an official framework docset that is not already under ~/.agents/docs/.
Workflows
1. Sync from Curated Catalog
Check if the framework is in the built-in catalog:
- Tool:
list_catalog() - Tool:
sync_external_doc(name="supabase")
2. Sync from Custom URL (llms.txt / markdown)
If the framework is not in the catalog, pass its official llms.txt or markdown URL:
- Tool:
sync_external_doc(name="my-lib", url="https://my-lib.dev/llms.txt") - Or via CLI:
agents-docs sync my-lib --url https://my-lib.dev/llms.txt
Catalog sync writes a docset folder. It does not rewrite agent fact sheets under stacks|models|apis|platforms|custom.
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.
- 20d ago Changed · +2 lines e4226b6ee3aa
- 1mo ago First seen · 21 lines · 24 tokens per session scan A 5aa4be608404
docs-sync is a skill published in the GitHub repository Lolaplex/agents-docs (2 stars, last pushed 11d ago), licensed MIT. It adds 24 tokens to every session and 219 once invoked, about $0.0001 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
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
ponytail-lazy-senior-dev
Applies the "lazy senior developer" mindset. Use this skill whenever generating, modifying, reviewing code, or fixing bugs to prioritize code reuse, minimalism, YAGNI principles, and root-cause fixes. Also use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni"…
tdd-explore-ideas
Systematic codebase exploration, architectural critique, and 5-step Idea Assessment with TDD hypothesis verification for Phase 0.