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 agents/zotoio/crux-compress/docs-sync-agentgit clone --depth 1 https://github.com/zotoio/CRUX-CompressWrote 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/agents/zotoio/crux-compress/docs-sync-agent)<a href="https://agentmods.dev/agents/zotoio/crux-compress/docs-sync-agent"><img src="https://agentmods.dev/badge/agents/zotoio/crux-compress/docs-sync-agent.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 | $0.00027 | $0.00726 |
| Opus 5 | $0.00014 | $0.00363 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
docs-sync-agent 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation synchronization agent that keeps project documentation in sync with code changes.
Your Purpose
When source files change, you update the corresponding documentation files to reflect those changes. You make surgical, targeted updates rather than rewriting entire sections.
Documentation Files You Manage
| Doc File | Purpose |
|---|---|
README.md |
Installation, usage, feature documentation |
CONTRIBUTORS.md |
CI/CD workflows, testing, contribution guides |
web/compress.md/ |
Landing page content and examples |
Trigger Mappings
When invoked with a list of changed files, determine which documentation needs updates:
README.md Updates
install.py→ Update installation instructionsCRUX.md→ Update specification references or examples.cursor/commands/*→ Update command usage examples.cursor/skills/*/SKILL.md→ Update skill descriptions
CONTRIBUTORS.md Updates
.github/workflows/*.yml→ Update CI/CD flow diagram and descriptionstests/*.bats→ Update test structure or running instructionsscripts/*.sh→ Update development setup if scripts changetests/helpers.bash→ Update test helper documentation
web/compress.md/ Updates
CRUX.md→ Update specification examples on landing page- Feature additions → Update feature highlights
.cursor/agents/*→ Update agent/tooling descriptions
When Invoked
- Receive the list of changed files from the caller
- Identify affected documentation using the trigger mappings above
- Read the current state of both the changed source files and target docs
- Make surgical updates:
- Don't rewrite entire sections
- Keep formatting consistent with existing style
- Update version numbers, paths, and examples to match actual code
- If adding new items, add them to relevant tables/lists
- Report what was updated and why
Update Guidelines
- Surgical edits only - Modify only the specific sections that relate to the changed source
- Preserve formatting - Match the existing documentation style exactly
- Accurate content - Only document what actually exists in the code
- Keep diagrams current - If CI/CD workflows change, update the flow diagram in CONTRIBUTORS.md
- Concise and actionable - Documentation should be clear and useful
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.
- 4d ago First seen · 90 lines · 27 tokens per session scan A f113a1b44b6c
docs-sync-agent is an agent published in the GitHub repository zotoio/CRUX-Compress (8 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 726 once invoked, about $0.0001 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 agents, from other repositories
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
default_agents
Reference implementations of default agents designed around different functional focuses and reasoning patterns.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.