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/sapientpants/deepsource-mcp-server/update-dependenciesgit clone --depth 1 https://github.com/sapientpants/deepsource-mcp-serverWhat 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.01187 |
| Opus 5 | $0.00000 | $0.00593 |
| Sonnet 5 | $0.00000 | $0.00237 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
update-dependencies 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Dependencies
You are about to update the dependencies of the project. This command helps maintain the project's dependencies while adhering to the established CI/CD workflow and changeset requirements.
Workflow Steps
1. Create a Feature Branch
Create a new branch following the naming convention:
git checkout -b chore/update-dependencies-<date>
# Example: chore/update-dependencies-2024-01
2. Update Dependencies
For Production Dependencies:
# Check outdated packages
pnpm outdated
# Update all dependencies to latest
pnpm update --latest
# Or update specific packages
pnpm update <package-name> --latest
For Dev Dependencies:
# Update dev dependencies
pnpm update --latest --dev
3. Install and Lock Dependencies
# Ensure pnpm-lock.yaml is updated
pnpm install
# Deduplicate dependencies if needed
pnpm dedupe
4. Test the Updates
Run the full verification suite to ensure compatibility:
# Run all checks (audit, typecheck, lint, format, test)
pnpm verify
# Run specific checks if needed
pnpm test
pnpm typecheck
pnpm lint
5. Create a Changeset
IMPORTANT: The CI/CD pipeline requires changesets for all changes. Choose the right type based on impact:
When to Use Empty Changeset
Use pnpm changeset --empty for changes that don't affect users:
- Dev dependency updates only
- CI/CD configuration changes
- Test-only improvements
- Internal tooling updates
- Documentation changes
# Create an empty changeset (no version bump)
pnpm changeset --empty
# The changeset message should document:
# - Which dependencies were updated
# - Why they were updated
# - Any tooling changes developers should know about
When to Use Regular Changeset
Use pnpm changeset for changes that affect the package/application:
- Production dependency updates
- Security fixes visible to users
- Breaking changes in dependencies
- Bug fixes from dependency updates
- New features from dependency updates
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 · 229 lines · 0 tokens per session scan A d8b77554e9cf
update-dependencies is a command published in the GitHub repository sapientpants/deepsource-mcp-server (7 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,187 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-31.
Other commands, from other repositories
release
Comprehensive workflow for releasing a new version of the VectorMCP Ruby gem following best practices.
release
Run the standard release flow — bump version, commit, push, open PR, merge, tag, create GitHub release. Use when shipping a new version of gsd-taskmanager.
go
Implement the agreed spec, ship to main, and deploy to the cluster — the dark-factory one-keystroke. Run from inside a feature worktree.
land
End-of-session wrap-up — commit WIP, sync onto main, gate against the worktree, then squash-merge to main. Runs the deterministic scripts/ship. Run from inside a feature worktree.
10-optimization-finalization
Comprehensive Optimization: Multi-agent optimization, PRD improvement, documentation consolidation, and production-ready finalization.
methodology
View your cognitive methodology profile and reasoning patterns.