salesforce-claude-code: Agent for Claude Code

.cursor/agents/doc-updater.md

doc-updater is an agent for Claude Code, Cursor from jiten-singh-shahi/salesforce-claude-code. It costs 54 tokens per session (1,939 once invoked), scanned A, original, MIT.

A documentation assistant that keeps Salesforce project documents aligned with the code and architectural decisions. It extracts facts from the project rather than inventing documentation.

In plain words
What is it for?
Use it to update READMEs, codemaps, data dictionaries, architecture records, deployment runbooks, and Apex or component documentation, and to find stale docs.
Why use it?
It reduces outdated or inconsistent documentation after code changes, planning work, or sprints.

Agent for Claude CodeCursor

Written for Claude Code and Cursor: shipped in a Claude Code plugin, but also installed under .cursor/. Also seen: model in frontmatter; mentions CLAUDE.md.

This is jiten-singh-shahi/salesforce-claude-code's own configuration. It tells Claude Code and Cursor how to work on salesforce-claude-code 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 salesforce-claude-code configures →

Part of the salesforce-claude-code plugin — 41 skills, 17 agents shipped together

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/agents/doc-updater.md
Clone the repo
git clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-code

Made for: Claude Code, Cursor.

Or install salesforce-claude-code, the plugin that ships this one along with the rest of its 41 skills, 17 agents.

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 doc-updater

README.md
[![agentmods](https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/doc-updater.svg)](https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/doc-updater)
Your own site
<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>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,939 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.00054 $0.01939
Opus 5 $0.00027 $0.00970
Sonnet 5 $0.00011 $0.00388
Haiku 4.5 $0.00005 $0.00194

Measured 8d ago against content hash 0d05ad27a49b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

.cursor/agents/doc-updater.md · 220 lines

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

  1. Read sfdx-project.json for project structure and package directories
  2. Glob *.cls, *.trigger, *.flow-meta.xml, lwc/*/ — build complete inventory
  3. Glob *.object-meta.xml — inventory objects, fields, relationships
  4. Check docs/ directory for existing documentation
  5. 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

Read the full file on GitHub · 220 lines

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. 8d ago First seen · 220 lines · 54 tokens per session scan A 0d05ad27a49b

Subscribe to this mod's changes

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.

Related

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.

travisjneuman/.claude · 69 tokens

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…

travisjneuman/.claude · 80 tokens

whitepaper-coherence

Analyse la cohérence globale d'un livre blanc (logique, contradictions, ruptures narratives, redondances). Utiliser pour auditer un whitepaper avant publication.

FlorianBruniaux/claude-code-ultimate-guide · 39 tokens

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…

Kanevry/session-orchestrator · 249 tokens

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…

KevinZai/commander · 34 tokens

verifier

Post-execution verification agent. Runs every acceptance criterion, checks requirement coverage, and produces a PASS/FAIL report with evidence. Never skips a criterion.

randomittin/heimdall · 33 tokens