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 commands/ehebert7/salesforce-claude-framework/dev-docs-updategit clone --depth 1 https://github.com/ehebert7/salesforce-claude-frameworkWhat 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.00000 | $0.00117 |
| Opus 5 | $0.00000 | $0.00059 |
| Sonnet 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 2d 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.
- 2d 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 (11 stars, last pushed 9mo 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
speckit.plan
Execute the implementation planning workflow using the plan template to generate design artifacts.
speckit.implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.
speckit.specify
Create or update the feature specification from a natural language feature description.
speckit.constitution
Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.