Borrowing it
Nothing to install: this file belongs to Caldis/react-zmage. 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/Caldis/react-zmage/master/.agents/skills/sync-public-docs/SKILL.mdgit clone --depth 1 https://github.com/Caldis/react-zmageWrote 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/caldis/react-zmage/sync-public-docs)<a href="https://agentmods.dev/skills/caldis/react-zmage/sync-public-docs"><img src="https://agentmods.dev/badge/skills/caldis/react-zmage/sync-public-docs/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/caldis/react-zmage/sync-public-docs"><img src="https://agentmods.dev/badge/skills/caldis/react-zmage/sync-public-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 69 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Excessive Agency · line 170 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00203 | $0.03396 |
| Opus 5.5 | $0.00081 | $0.01358 |
| Sonnet 5.5 | $0.00041 | $0.00679 |
| Haiku 4.5 | $0.00020 | $0.00340 |
Grade A, and why
sync-public-docs 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 2mo 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync public docs (react-zmage)
Why this skill exists
The repo has four "outward-facing" documentation surfaces and only two of them are guarded automatically:
| Destination | Source of truth | Auto-guard? |
|---|---|---|
packages/core/src/types/ |
itself | — (this IS the source) |
packages/home/src/schema/param-schema.ts |
imports BaseType from react-zmage (typed) but defaults are hand-copied |
✅ types only; ❌ default values |
packages/home/src/docs/sections/*.tsx + i18n keys |
hand-written prose | ❌ |
packages/home/src/playground/* + routes/playground/* |
hand-written examples | ❌ |
docs/llms.txt |
checked-in file served as /llms.txt |
✅ static contract tests, ❌ content is still hand-written |
packages/llms-eval/eval.test.mjs (11-item contract) |
llms.txt ↔ core |
✅ but manual run only |
README.md / AGENTS.md |
hand-written | ❌ |
When core's public API changes, drift across these surfaces is silent — TS will flag a renamed type symbol but won't flag a stale default value, an outdated prop description in Props.tsx, or a removed prop still mentioned in README.md.
The cost of drift is real: README is what npm shows; llms.txt is what AI agents read; home/docs is what the live site renders. They can each go wrong independently.
When to invoke
Strong triggers (just do it):
- Any change to
packages/core/src/types/global.ts,types/default.ts, orindex.ts - Any change to
packages/core/package.jsonexportsfield,peerDependencies, orversion - Adding, renaming, or removing a prop on
<Zmage> - Changing a default value in
defPropordefPreset - Changing the static method surface of
Zmage(e.g. adding a newZmage.X) - Changing what
react-zmage/ssrexports - The user says "sync docs", "propagate this", "update public docs", "同步文档", "准备发版"
Weak triggers (consider, then judge):
- Pure internal refactors that don't change public types or defaults — usually skip
- Documentation-only PRs that already touch one destination — still run steps 5–6 to verify the others didn't drift
- Tooling/build config changes — only if they alter
exports, peerDeps, or what consumers see
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.
- 2mo ago First seen · 171 lines · 203 tokens per session scan A b55ae7d49707
sync-public-docs is a skill published in the GitHub repository Caldis/react-zmage (943 stars, last pushed 5mo ago), licensed MIT. It adds 203 tokens to every session and 3,396 once invoked, about $0.0008 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-30.
sync-public-docs compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sync-public-docsCaldis/react-zmage | Skill | 943 | 5mo ago | MIT | A | 203 | Claude Code, Codex |
| 3d-web-experienceranbot-ai/awesome-skills | Skill | 8 | yesterday | none | A | 45 | Claude Code, Codex |
| add-app-clipranbot-ai/awesome-skills | Skill | 8 | yesterday | none | A | 54 | Claude Code, Codex |
| angularranbot-ai/awesome-skills | Skill | 8 | yesterday | none | A | 32 | Claude Code, Codex |
| build-ghost-appTryGhost/Ghost | Skill | 56k | today | MIT | A | 44 | Claude Code, Codex |
| chakra-ui-builderchakra-ui/chakra-ui | Skill | 41k | yesterday | MIT | A | 214 | Claude Code, Codex |
| material-ui-tailwindmui/material-ui | Skill | 99k | yesterday | MIT | A | 67 | Claude Code, Codex |