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/mongodb/mongo-java-driver/sync-agents-docsnpx skills add mongodb/mongo-java-driver --skill sync-agents-docsgit clone --depth 1 https://github.com/mongodb/mongo-java-driverWhat 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.00043 | $0.00378 |
| Opus 5 | $0.00022 | $0.00189 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
sync-agents-docs 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.
What it actually says
Sync Documentation After Build Changes
This is a manual checklist — disable-model-invocation: true means agents cannot execute it autonomously.
Human developers should walk through this after buildSrc changes.
After modifying buildSrc or build conventions, check whether AGENTS.md files, skills, and references need updating.
Review your changes against the checklist below and update only the affected files.
Checklist
| What changed | What to update |
|---|---|
Formatting conventions (spotless.gradle.kts) |
Root AGENTS.md Style section, style-reference reference, affected module AGENTS.md files |
| Convention plugins added or removed | buildSrc/AGENTS.md plugin table, root AGENTS.md if build commands or workflow changed |
Testing conventions (testing-*.gradle.kts) |
Root AGENTS.md Testing section, testing-guide reference, affected module AGENTS.md files |
| Project plugins added or removed | buildSrc/AGENTS.md project plugin table |
| Build commands or task names changed | Root AGENTS.md Build and Before Submitting sections, evergreen skill, module AGENTS.md files |
| CI/CD or publishing changes | evergreen skill |
How to use
- Review the diff of your buildSrc changes
- Walk through the checklist above — only rows matching your changes need action
- Update the affected files, keeping changes minimal and accurate
- Verify no stale references remain (e.g., renamed tasks, removed plugins)
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 · 31 lines · 43 tokens per session scan A 383a547cdfd0
sync-agents-docs is a skill published in the GitHub repository mongodb/mongo-java-driver (2,660 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 378 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
java-kotlin
Java and Kotlin programming patterns.
write-fixture
Write Java/Kotlin tests with Fixture Monkey — enumerate the cases a method can produce, pick the ones worth testing, and build each fixture pinning only the properties that force the expected outcome.
plugin-code-review-orchestrated
Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.
github-issue-manager
Classifies a user request as Bug, Compatibility, Feature, Question, or Task for the explyt/spring-plugin GitHub repo, lightly researches the relevant codebase, searches similar existing issues, and either reports an existing issue or creates a correctly titled and labeled one following the repository issue forms. Use…
review-async-lifecycle
Normative reviewer for EDT safety, coroutines, cancellation, read/write actions, disposal, listeners and async lifecycle in the explyt spring-plugin. Use during orchestrated code review when the diff touches threading, background tasks, read or write actions, listeners, MessageBus, Disposable ownership or progress…
review-core-correctness
Normative mandatory reviewer for correctness, contracts, architecture sanity, UX behavior, code quality and tests in the explyt spring-plugin codebase. Use during orchestrated code review of a PR, diff, commit or branch, or when asked to review correctness, logic, architecture or test coverage of plugin changes.