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-docnpx skills add apache/tinkerpop --skill tinker-docgit 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.00096 | $0.01893 |
| Opus 5 | $0.00048 | $0.00946 |
| Sonnet 5 | $0.00019 | $0.00379 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
tinker-doc 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TinkerPop Documentation Skill
This skill is about the craft of TinkerPop documentation: getting the voice, audience, and shape of each kind of document right. The mechanics that keep the build green (executable code blocks, AsciiDoc wiring) are covered in the references and matter, but they serve the writing, not the other way around.
All project documentation lives under docs/src/ and is AsciiDoc, never
Markdown. It is organized into several books, each with its own audience and
purpose. The four directories under docs/src/dev/ are themselves separate
books, not one:
| Book | Path | Audience | Purpose |
|---|---|---|---|
| Reference | docs/src/reference/ |
Users | The complete, authoritative description of every feature and step |
| Recipes | docs/src/recipes/ |
Users | Reusable problem→solution patterns for real tasks |
| Tutorials | docs/src/tutorials/ |
Users (learning) | Story-driven walkthroughs of a focused topic |
| Upgrade | docs/src/upgrade/ |
Users (upgrading) | Announces what changed in a release and how to adapt |
| Provider | docs/src/dev/provider/ |
Graph providers | Implementation guidance, provider policies, and the canonical Gremlin semantics |
| IO | docs/src/dev/io/ |
Providers and advanced users | The serialization formats (GraphBinary, GraphSON, GraphML, Gryo) |
| Developer | docs/src/dev/developer/ |
Contributors | Contributing, development environment, committer and release process |
| Future | docs/src/dev/future/ |
Contributors | Design proposals for planned or possible changes |
The full per-book voice guide, with grounded examples from the real docs, is in references/books-and-voice.md. Read it before writing in any book you have not written in before. The short version of each book's character:
- Upgrade announces. It tells a feature's story — what changed and why it
matters — and defers exhaustive detail to the reference docs via
See:rather than cataloging every edge case itself. A typical entry is short: a paragraph or two and one example. It frames past shortcomings positively and treats breaking changes as a priority. - Reference and Recipes instruct. They are the focal point for correct usage and established patterns: complete, user-friendly, and formal.
- Tutorials teach through a story but otherwise follow the Reference/Recipes style.
- Provider documents internals in the Reference/Recipes style. The
gremlin-semantics.asciidocfile is special and load-bearing (see below). - IO specifies the serialization formats in the same formal, complete style as Provider.
- Developer docs are internal notes, instructions and standard processes for contributors.
- Future holds design proposals for changes under consideration.
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.
- 2d ago First seen · 142 lines · 96 tokens per session scan A 065ac44c06d7
tinker-doc is a skill published in the GitHub repository apache/tinkerpop (2,144 stars, last pushed 4d ago), licensed Apache-2.0. It adds 96 tokens to every session and 1,893 once invoked, about $0.0005 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'.
dkg-node
The DKG V10 Node is your primary memory system. This skill teaches you to operate your node's three-layer verifiable memory — write and retrieve private drafts in Working Memory, share with peers in Shared Working Memory, and publish permanently to Verifiable Memory on-chain.
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/.
high-end-visual-design
Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and animations that make a website feel expensive. Blocks all the common defaults that make AI designs look cheap or generic.
deep-reading-analyst
“用于文章、论文和长篇内容的深度拆解与理解框架，内置 10+ 种思考模型（SCQA、5W2H、批判性思维、逆向思维、心智模型、第一性原理、系统思维、六顶思考帽等）。当用户想要：① 深入理解复杂文章/内容，② 分析论证并识别逻辑漏洞，③ 从阅读材料中提炼可执行洞见，④ 产出读书笔记或学习总结，⑤ 对比多篇来源，⑥ 将知识转化为实际应用，或 ⑦ 使用特定思维框架时使用本技能。典型触发语包括：”帮我分析这篇文章””帮我理解这段内容””深度拆解一下””从这篇文章里提炼要点/洞见””按某个框架分析””我给你一个链接/长文，请帮我分析”等。”.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.