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 skills/futuresearch/futuresearch-python/bump-sdk-versionnpx skills add futuresearch/futuresearch-python --skill bump-sdk-versiongit clone --depth 1 https://github.com/futuresearch/futuresearch-pythonWhat 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.00040 | $0.01377 |
| Opus 5 | $0.00020 | $0.00688 |
| Sonnet 5 | $0.00008 | $0.00275 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
bump-sdk-version 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bump SDK Version
Versioning Guidelines
We use semantic versioning (MAJOR.MINOR.PATCH) while at major version 0:
| Bump | When | Examples |
|---|---|---|
| Patch (0.8.0 -> 0.8.1) | Bug fixes, docs changes, small tweaks, dependency updates | Fix a typo in output, update a dependency |
| Minor (0.8.1 -> 0.9.0) | New features, new operation types, API additions | Add a new operation, new SDK method, new MCP tool |
| Patch for breaking changes that are trivial to adapt | Rename a parameter, change a default | Rename max_rows to row_limit |
| Minor for breaking changes that require migration | Remove or restructure API surface | Remove an operation type, change return format |
If unsure, ask the user which component to bump.
Files to Update
All paths are relative to futuresearch-python/. Update the version string in each:
pyproject.toml—project.version(the source of truth).claude-plugin/plugin.json—version.claude-plugin/marketplace.json—plugins[0].versiongemini-extension.json—versionfuturesearch-mcp/pyproject.toml—project.versionANDdependencies(futuresearch>=X.Y.Z)futuresearch-mcp/server.json—versionANDpackages[0].versionfuturesearch-mcp/manifest.json—versionCITATION.cff—versionANDdate-released(set to today's date)README.md— BibTeXversionfield in the citation blockstubs/everyrow/pyproject.toml—project.versionANDdependencies(futuresearch>=X.Y.Z)stubs/everyrow-mcp/pyproject.toml—project.versionANDdependencies(futuresearch-mcp>=X.Y.Z)
After editing, regenerate the lock files. Run uv lock in futuresearch-python/ first:
cd futuresearch-python && uv lock
Then sync transitive lockfiles across the entire monorepo. The CI check
check-uv-sync runs ./uv-all.sh sync --all-extras --dev --all-groups and
will fail if any other workspace's uv.lock still references the old SDK
version. Run it from the repo root:
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 · 123 lines · 40 tokens per session scan A 8ade5dad2dae
bump-sdk-version is a skill published in the GitHub repository futuresearch/futuresearch-python (54 stars, last pushed 5d ago), licensed MIT. It adds 40 tokens to every session and 1,377 once invoked, about $0.0002 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.
Other skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat features.
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.