Apache TinkerPop is a graph-computing framework for applications that store or analyze connected data, such as property graphs in databases. Developers use its Gremlin traversal language, drivers, servers, and tools to work with different graph systems through a common interface.
Borrowing it
Nothing to install: this file belongs to apache/tinkerpop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/apache/tinkerpop/master/.skills/tinker-merge/SKILL.mdgit clone --depth 1 https://github.com/apache/tinkerpopWrote 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/apache/tinkerpop/tinker-merge)<a href="https://agentmods.dev/skills/apache/tinkerpop/tinker-merge"><img src="https://agentmods.dev/badge/skills/apache/tinkerpop/tinker-merge/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/apache/tinkerpop/tinker-merge"><img src="https://agentmods.dev/badge/skills/apache/tinkerpop/tinker-merge.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00073 | $0.01411 |
| Opus 5.5 | $0.00029 | $0.00564 |
| Sonnet 5.5 | $0.00015 | $0.00282 |
| Haiku 4.5 | $0.00007 | $0.00141 |
Grade A, and why
tinker-merge 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 today.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TinkerPop Merge Skill
TinkerPop merges through its oldest release branch toward master: work that lands on 3.7-dev
is merged into 3.8-dev, and 3.8-dev into master. scripts/merge-forward.sh performs that
chain deterministically. Your part is the one question to the operator, the conflicts, and the
handoff. The branch rules behind it are in the Branches and Pull Requests sections of
docs/src/dev/developer/for-committers.asciidoc.
Never push. The run ends with local merges and a printed push command. The operator reviews
the result and pushes it. That rule in AGENTS.md has no exception here.
1. Identify the source
The operator names what to merge. Pass it to the script as is:
| The operator says | Source argument |
|---|---|
| a pull request number | #1234 |
| a feature branch | the branch name, e.g. TINKERPOP-1234 |
| "merge 3.7-dev through" after committing to it directly | the release branch, e.g. 3.7-dev |
The script works out the chain itself: from the pull request's base branch, from the release
branch a feature branch was cut from, or from the named release branch. Pass --onto <branch>
only when the operator states the target or the script says it cannot tell.
2. Ask how to test — the only question
Ask the operator exactly this, with the default first:
mvn clean install(default) →--test defaultmvn clean install -DskipIntegrationTests=false→--test integration- Skip all testing →
--test skip - A command the operator gives →
--test-command '<command>'
Ask nothing else before starting. Whichever command is chosen runs from the repository root on
every branch in the chain, after its merge, and a non-zero exit counts as a test failure. Pass
an operator's command through exactly as given, quoted as one argument.
GLV modules are tested only where the clone has activated them (see the tinker-dev skill), so
say so if the operator chose testing and a GLV changed but its .glv sentinel is absent.
3. Check the JDK for each branch
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 125 lines · 73 tokens per session scan A 13f952bb22b4
tinker-merge is a skill published in the GitHub repository apache/tinkerpop (2,150 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 1,411 once invoked, about $0.0003 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-10-29.
Other skills, from other repositories
release
Used to release all toolbox, integrations, agents. Use when releasing a subproject to PyPI, Docker Hub, or when the user asks to release or publish.
changelog
Use after any code change (feature, fix, refactor, review fixup) to update /changelogs/YYYY-MM-DD.log and run the test suite. Mandatory post-change routine — see .cursorrules.
source-command-github-release-manager
Migrated source command github-release-manager.
source-command-github-sync-coordinator
Migrated source command github-sync-coordinator.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.