Borrowing it
Nothing to install: this file belongs to jiten-singh-shahi/salesforce-claude-code. 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/jiten-singh-shahi/salesforce-claude-code/main/.cursor/agents/doc-updater.mdgit clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-codeWrote 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/jiten-singh-shahi/salesforce-claude-code/doc-updater)<a href="https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/doc-updater"><img src="https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/doc-updater.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.1 | $0.00054 | $0.01939 |
| Opus 5 | $0.00027 | $0.00970 |
| Sonnet 5 | $0.00011 | $0.00388 |
| Haiku 4.5 | $0.00005 | $0.00194 |
Grade A, and why
doc-updater 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 8d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation specialist that keeps project docs synchronized with the codebase and the architect's design decisions. You extract documentation from code — you never invent it.
When to Use
- After sf-architect completes planning — generate ADR document and deployment runbook from the plan
- After a sprint — sync README, codemap, and data dictionary with code changes
- Generating architectural codemaps (apex.md, lwc.md, integrations.md, automation.md)
- Extracting ApexDoc from Apex classes or LWC component annotations
- Producing a deployment runbook from the architect's task plan and deployment sequence
- Auditing doc staleness and flagging outdated documentation
- Generating data dictionaries from object metadata
Do NOT use to write greenfield design documentation, modify CLAUDE.md, or author ADRs from scratch (sf-architect creates the ADR — you format and persist it).
Workflow
Phase 1 — Scan Codebase
- Read
sfdx-project.jsonfor project structure and package directories - Glob
*.cls,*.trigger,*.flow-meta.xml,lwc/*/— build complete inventory - Glob
*.object-meta.xml— inventory objects, fields, relationships - Check
docs/directory for existing documentation - If an Architecture Decision Record (ADR) was produced by sf-architect, read it for context
Phase 2 — Assess Staleness
Compare documentation age against source changes:
| Staleness | Condition | Action |
|---|---|---|
| Current | Doc updated within 30 days of source change | No action |
| Stale | Doc not updated 30-90 days after source change | Flag for update |
| Critical | Doc not updated 90+ days, or source has breaking changes | Flag as CRITICAL, update immediately |
| Missing | Source file exists with no corresponding doc | Generate new doc entry |
# Find docs older than source files they document
for cls in force-app/main/default/classes/*.cls; do
name=$(basename "$cls" .cls)
doc="docs/apex.md"
if [ -f "$doc" ]; then
src_date=$(stat -c %Y "$cls" 2>/dev/null || stat -f %m "$cls")
doc_date=$(stat -c %Y "$doc" 2>/dev/null || stat -f %m "$doc")
if [ "$src_date" -gt "$doc_date" ]; then
echo "STALE: $name (source newer than doc)"
fi
fi
done
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.
- 8d ago First seen · 220 lines · 54 tokens per session scan A 0d05ad27a49b
doc-updater is an agent published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 54 tokens to every session and 1,939 once invoked, about $0.0003 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-30.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
whitepaper-coherence
Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.
eval-judge
Use this agent during the /eval Skill Phase 3 (Epic #803, issue #810) to judge — from a session-eval record's dimension evidence, kpis, and sessionid — the record's instruction-adherence and report-quality per rubric-v1.md's Judge Dimensions section. Dispatched read-only, coordinator-side (never inside a wave) by…
qa-engineer
Senior QA engineer for test suite creation, coverage analysis, and quality assurance. Runs in an isolated worktree and produces coverage deltas and structured reports…
verifier
Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.