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 skills add futuresearch/futuresearch-python --skill bump-sdk-versiongit clone --depth 1 https://github.com/futuresearch/futuresearch-pythonWrote 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/skills/futuresearch/futuresearch-python/bump-sdk-version)<a href="https://agentmods.dev/skills/futuresearch/futuresearch-python/bump-sdk-version"><img src="https://agentmods.dev/badge/skills/futuresearch/futuresearch-python/bump-sdk-version/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/skills/futuresearch/futuresearch-python/bump-sdk-version"><img src="https://agentmods.dev/badge/skills/futuresearch/futuresearch-python/bump-sdk-version.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00040 | $0.01377 |
| Opus 5.5 | $0.00016 | $0.00551 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (57 stars, last pushed 11d ago), licensed MIT. It adds 40 tokens to every session and 1,377 once invoked, about $0.0002 per session on Opus 5.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
tmb_push-gate
Bro's push-gate orchestration — reaping unsigned commits, spawning pr-reviewer per task, and the all-pass push + PR-create + post-merge cleanup path. Loaded by bro when the push hook blocks or the Human asks for review-before-push.
gh-pr-merge-unstable-state-needs-auto-and-watch-branch-deletes
Diagnose and recover from two adjacent gh pr merge failure modes that masquerade as merge conflicts. Use when: (1) gh pr merge --squash (or --merge) errors with "To have the pull request merged after all the requirements have been met, add the --auto flag" AND "Run the following to resolve the merge conflicts locally"…
merge-queue-thrash-stop-inflow-and-open-prs-as-drafts
When main moves faster than the slowest CI leg, every open branch goes stale before it can merge and the whole queue jams with nothing red. Use when: (1) several PRs sit at mergeStateStatus BEHIND with auto-merge armed and none of them lands; (2) branches are being updated, re-running CI and going stale again before…
scheduled-fallback-check-cites-stale-task-id
Don't act on a background-task ID embedded in an incoming check-in message (a self-scheduled fallback wakeup, a peer's "did it finish?" ping, a cron reminder) without first verifying it's still the CURRENT run. Use when: (1) you dispatched a long-running background task (a local CI-equivalent gate run, a build, a…
subagent-reports-complete-but-pr-unmerged
Catch the systematic gap between sub-agent "completed" status and the actual end state of a PR-merge orchestration task. Use when: (1) you've dispatched multiple parallel sub-agents (general-purpose or specialist) to open + review + merge PRs, (2) the parent receives with status: completed but the sub-agent's last…
release-check
Pre-release verification with structured report. Validates test coverage, security status, CHANGELOG completeness, dependency freshness, tech debt severity. Outputs GO/NO-GO recommendation with confidence score and specific remediation steps.