Borrowing it
Nothing to install: this file belongs to ehebert7/salesforce-claude-framework. 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/ehebert7/salesforce-claude-framework/master/.claude/commands/dev-docs-update.mdgit clone --depth 1 https://github.com/ehebert7/salesforce-claude-frameworkWrote 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/commands/ehebert7/salesforce-claude-framework/dev-docs-update)<a href="https://agentmods.dev/commands/ehebert7/salesforce-claude-framework/dev-docs-update"><img src="https://agentmods.dev/badge/commands/ehebert7/salesforce-claude-framework/dev-docs-update/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/commands/ehebert7/salesforce-claude-framework/dev-docs-update"><img src="https://agentmods.dev/badge/commands/ehebert7/salesforce-claude-framework/dev-docs-update.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.00000 | $0.00117 |
| Opus 5.5 | $0.00000 | $0.00047 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
dev-docs-update 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.
What it actually says
Update dev docs before compacting or ending session:
- Find active task in
dev/active/ - Update
[task-name]-context.md:- Set "Last Updated" to current timestamp
- Update "Current State" with progress
- Update "Next Steps" with what to do next
- Add any new "Important Decisions Made"
- Update
[task-name]-tasks.md:- Move completed items to "Completed" section
- Update "In Progress" with current work
- Confirm updates to user
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.
- 2mo ago First seen · 13 lines · 0 tokens per session scan A 8a6cb2e76ce6
dev-docs-update is a command published in the GitHub repository ehebert7/salesforce-claude-framework (12 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 117 tokens. 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 commands, from other repositories
API_REFERENCE
Generated from commands/specs/.json. Do not edit this file directly.
build-skills
End-to-end orchestrator that takes a count + optional topic hints and ships N production-grade skills with measurement-driven quality gates at every step.
onboard-source
One entrypoint for turning outside knowledge into catalog-quality skills.
clarify-requirements
Wraps agents/requirements-clarifier/AGENT.md. Takes one requirement — a paragraph, a worksheet, a backlog extract — searches local coverage for every capability it implies, harvests every row of every matching skill's ## Questions to Ask Before Configuring table, dedupes by meaning, proposes a default per question…
plan-build
Wraps agents/build-planner/AGENT.md. Takes a build directory whose plan.json is past gate G1 and writes the plan the rest of the loop executes: scope in and out, a fit-gap entry per capability, a decision per technology choice with the decision-tree branch that produced it, two to six milestones, and the ordered steps…
verify-plan
Wraps agents/plan-verifier/AGENT.md. For every step in plan.json it runs three independent adversarial lenses — executability (can the named agent actually produce these outputs from these inputs, and is it eligible to own the step in this buildmode?), grounding (do the cited skills, templates and decision-tree…