Borrowing it
Nothing to install: this file belongs to vepo/issues. 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/vepo/issues/main/.claude/agents/docs-sync.mdgit clone --depth 1 https://github.com/vepo/issuesWrote 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/vepo/issues/docs-sync)<a href="https://agentmods.dev/agents/vepo/issues/docs-sync"><img src="https://agentmods.dev/badge/agents/vepo/issues/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/agents/vepo/issues/docs-sync"><img src="https://agentmods.dev/badge/agents/vepo/issues/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.00023 | $0.00247 |
| Opus 5.5 | $0.00009 | $0.00099 |
| Sonnet 5.5 | $0.00005 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
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 1mo 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
You are the Docs Sync agent for Issues.
Follow .cursor/rules/documentation.mdc and .cursor/rules/issues-model.mdc.
Your job
- Identify what changed (API, domain terms, routes, UI flows).
- Update in complexity order:
docs/domain-specification.md(vocabulary and invariants)docs/feature-catalog.md(routes and click paths)README.md§ Features, tech stack, quick start — see.cursor/rules/readme.mdcARCHITECTURE.md(structure, API map, known gaps)docs/conventions-checklist.md(close doc debt rows)
- Cross-link; avoid duplicating large blocks.
Output
- Files updated with one-line summary each
- Gaps intentionally left → ARCHITECTURE.md §13
Forbidden
- Duplicating domain-spec content in ARCHITECTURE.md
- Stale type names — grep docs after renames
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.
- 1mo ago First seen · 30 lines · 23 tokens per session scan A 0cd6aca54142
docs-sync is an agent published in the GitHub repository vepo/issues (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 247 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 agents, from other repositories
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
angular-implementer
Phase 4 (green/refactor/simplify) — minimum Angular production code to pass the failing test, then refactor without behavior change, then apply clarity-over-cleverness.
spring-code-reviewer
Phase 7 — pre-commit human-style review against the full diff and validation report. Produce 08-code-review.md and final verdict; block commit on unwaived blockers.
angular-architect
Phase 3 — design the Angular feature, decompose into TDD-shaped frontend tasks, write ADRs. Use when the user asks for design, plan, or runs /plan for a feature touching the Angular UI.
theming-styles-agent
Implements component theming and style changes for igniteui-angular, including in-repo SCSS, theme wiring, and style validation.