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/apache/tinkerpop/tinker-devnpx skills add apache/tinkerpop --skill tinker-devgit clone --depth 1 https://github.com/apache/tinkerpopWhat 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.00075 | $0.01990 |
| Opus 5 | $0.00037 | $0.00995 |
| Sonnet 5 | $0.00015 | $0.00398 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
tinker-dev 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 yesterday.
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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TinkerPop Development Skill
Project Overview
Apache TinkerPop is a graph computing framework providing a standard API (the Gremlin graph traversal language) for graph databases and processors. The repository is a Maven multi-module monorepo that wraps JVM code, Python, JavaScript/TypeScript, .NET, and Go under a single build.
Canonical project documentation (prefer local files over external URLs):
README.mdandCONTRIBUTING.mdat the repo root- Reference docs:
docs/src/reference/ - Developer docs:
docs/src/dev/developer/ - Provider docs and Gremlin Semantics:
docs/src/dev/provider/ - IO and Serialization:
docs/src/dev/io/ - Recipes:
docs/src/recipes/ - Upgrade docs:
docs/src/upgrade/ - Future plans:
docs/src/dev/future/
Definition of Done
A change is not done until a full Maven validation has passed locally. Run it before presenting work for review — even when your targeted or unit tests already pass, and even if you judge a full run unnecessary. Incremental testing during development is encouraged, but it does not satisfy this gate.
Validation is two steps. First, rebuild and install the whole reactor so every module picks up your changes:
mvn clean install -DskipTests
Then run verify scoped to what you changed, using the broadest rule that applies, and
always list every module you touched.
Self-contained modules — changing one of these only requires validating that module:
| Changed module | Validate command |
|---|---|
| Python GLV | mvn verify -pl gremlin-python |
| JavaScript GLV | mvn verify -pl :gremlin-javascript |
| .NET GLV | mvn verify -pl :gremlin-dotnet,:gremlin-dotnet-source,:gremlin-dotnet-tests |
| Go GLV | mvn verify -pl :gremlin-go |
gremlint |
mvn verify -pl :gremlint |
gremlin-mcp |
mvn verify -pl :gremlin-mcp |
Other single JVM module (e.g. tinkergraph-gremlin, gremlin-console) |
mvn verify -pl <module> -DskipIntegrationTests=false |
Shared modules — depended on by others, so changing them means validating the consumers too. Use the broadest rule that matches:
What ships with it
4 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.
- yesterday First seen · 158 lines · 75 tokens per session scan A 94cea3a88ac9
tinker-dev is a skill published in the GitHub repository apache/tinkerpop (2,144 stars, last pushed 3d ago), licensed Apache-2.0. It adds 75 tokens to every session and 1,990 once invoked, about $0.0004 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
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
memgraph-storage-reviewer
Review code changes in Memgraph's storage layer, including MVCC, concurrency patterns, WAL, recovery, DDL operations, index/constraint management, delta chains, and skip list operations. Invoke for pull requests or changes to src/storage/v2/.
cognee-permissions
Use when working with cognee's permission system — understanding or changing how users, roles, and tenants get access to datasets, how ACL grants work, where permissions are enforced in add/cognify/search/delete, and how the grant records surface in the memory-provenance view.
cognee-cli
Use when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
cognee-community
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify)…
cognee-docker
Use when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.