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/aojdevstudio/dev-utils-marketplace/update-claudegit clone --depth 1 https://github.com/AojdevStudio/dev-utils-marketplaceWrote 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/aojdevstudio/dev-utils-marketplace/update-claude)<a href="https://agentmods.dev/commands/aojdevstudio/dev-utils-marketplace/update-claude"><img src="https://agentmods.dev/badge/commands/aojdevstudio/dev-utils-marketplace/update-claude.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 | $0.00013 | $0.00793 |
| Opus 5 | $0.00006 | $0.00396 |
| Sonnet 5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00001 | $0.00079 |
Grade A, and why
update-claude 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Claude.md
Use Serena-first analysis to update CLAUDE.md based on recent code changes and git history.
Variables
TARGET_DIRECTORY: {{if flags.directory}}{{flags.directory}}{{else}}.{{endif}} CLAUDE_FILE: {{if flags.directory}}{{flags.directory}}/CLAUDE.md{{else}}CLAUDE.md{{endif}} ANALYSIS_SCOPE: {{if flags.directory}}directory-specific{{else}}project-wide{{endif}}
Workflow
1. Initial Setup
- Check Serena onboarding:
mcp__serena__check_onboarding_performed - If not onboarded, complete onboarding process first
- Use
mcp__serena__think_about_task_adherenceto validate update scope
2. Git Analysis
- Get current status: !
git status --porcelain - Review recent commits: !
git log --oneline -10 - Analyze changed files: !
git diff HEAD~5 --name-only | head -20 - Check key file modifications: !
git diff --name-status HEAD~10 | grep "^M" | head -10 - Store git insights:
mcp__serena__write_memory --memory_name="git_analysis"
3. Serena Codebase Analysis
- Analyze directory structure:
mcp__serena__list_dir --relative_path="TARGET_DIRECTORY" --recursive=true - For each modified file from git analysis:
- Get symbol overview:
mcp__serena__get_symbols_overview --relative_path="<FILE>" - Find new symbols:
mcp__serena__find_symbol --name_path="<NEW_SYMBOLS>" - Check symbol impact:
mcp__serena__find_referencing_symbols --name_path="<KEY_SYMBOLS>"
- Get symbol overview:
- Store symbol analysis:
mcp__serena__write_memory --memory_name="symbol_changes"
4. Content Integration
- Read existing CLAUDE.md file: @CLAUDE_FILE
- Use
mcp__serena__think_about_collected_informationto validate analysis - Update CLAUDE.md based on @ai-docs/serena-enhanced-claude-template.md:
- Project overview with new architecture patterns
- Save updated CLAUDE.md to CLAUDE_FILE location
5. Validation
- Use
mcp__serena__think_about_whether_you_are_doneto verify completeness - Store update insights:
mcp__serena__write_memory --memory_name="claude_update_ANALYSIS_SCOPE"
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.
- 3d ago First seen · 86 lines · 13 tokens per session scan A e60c415a1f5d
update-claude is a command published in the GitHub repository AojdevStudio/dev-utils-marketplace (2 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 793 once invoked, about $0.0001 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.