agentmods.dev

remediate: Command for Claude Code

.claude/commands/sync-docs.md

sync-docs is a command for Claude Code from fvckprth/remediate. It costs 14 tokens per session (443 once invoked), scanned A, original, MIT.

A command for keeping a project's documentation, agent instructions, and README aligned after changes.

In plain words
What is it for?
Use it after changing recipes, properties, request data, component APIs, capture types, or server helpers so all three documentation sources match.
Why use it?
It prevents users and developers from finding different instructions in the docs site, skill file, and README.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is fvckprth/remediate's own configuration. It tells Claude Code how to work on remediate itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything remediate configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/parthpatel/Desktop/Projects/remediate-mktg/src/app/docs/.

not rated 12repo 1mo ago A scan 14 tokens original MIT
View source ↗ fvckprth/remediate remediate.ski
Reuse

Borrowing it

Nothing to install: this file belongs to fvckprth/remediate. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fvckprth/remediate/main/.claude/commands/sync-docs.md
Clone the repo
git clone --depth 1 https://github.com/fvckprth/remediate

Made for: Claude Code.

Wrote 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.

agentmods badge for sync-docs

README.md
[![agentmods](https://agentmods.dev/badge/commands/fvckprth/remediate/sync-docs/github.svg)](https://agentmods.dev/commands/fvckprth/remediate/sync-docs)
Your own site
<a href="https://agentmods.dev/commands/fvckprth/remediate/sync-docs"><img src="https://agentmods.dev/badge/commands/fvckprth/remediate/sync-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.

agentmods 80×15 button for sync-docs

Your own site · 80×15
<a href="https://agentmods.dev/commands/fvckprth/remediate/sync-docs"><img src="https://agentmods.dev/badge/commands/fvckprth/remediate/sync-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 443 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00443
Opus 5.5 $0.00006 $0.00177
Sonnet 5.5 $0.00003 $0.00089
Haiku 4.5 $0.00001 $0.00044

Measured 2mo ago against content hash 2ea73886c5f9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sync-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.

.claude/commands/sync-docs.md · 49 lines

What it actually says

Sync Docs

keep the docs site, agent skill, and package README in sync after changes.

when to run

after any change to: recipes, props, payload shape, component API, capture types, or server helpers.

sources of truth

  • docs site (/Users/parthpatel/Desktop/Projects/remediate-mktg/src/app/docs/) — the canonical reference
  • agent skill (skills/remediate/SKILL.md) — must match the docs recipes and component patterns
  • package README (README.md at repo root) — quick-start subset of the docs

steps

  1. identify what changed

    • if $ARGUMENTS is provided, use it as the description of what changed
    • if empty, diff the docs site against the skill and README to find mismatches

  2. read current state of all three

    • read the relevant docs pages (install, recipes, payload, reference)
    • read skills/remediate/SKILL.md
    • read README.md

  3. update the skill

    • sync recipe templates to match docs (same code, same type narrowing, same file handling)
    • sync backend detection signals if new backends were added
    • sync component mounting instructions if props changed
    • sync notes section if capture types or API changed

  4. update the README

    • sync the server route example to match the install page
    • sync the props table to match the reference page
    • sync capture type descriptions if they changed
    • keep the README minimal — it's a quick-start, not the full docs

  5. commit and push both repos

    • skill + README changes in the package repo: docs: sync skill and readme with docs site
    • if docs site needed fixes too, commit those separately in remediate-mktg

  6. confirm

    • list what was updated in each file
    • flag anything that looked inconsistent but wasn't clear how to resolve
Changes

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.

  1. 2mo ago First seen · 49 lines · 14 tokens per session scan A 2ea73886c5f9

Subscribe to this mod's changes

sync-docs is a command published in the GitHub repository fvckprth/remediate (12 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 443 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-30.

Writing and docs
Related

sync-docs compared with commands from other repositories

sync-docs next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sync-docsfvckprth/remediateCommand121mo agoMITA14Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code