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 agents/jonapoul/aktual/dependency-browsergit clone --depth 1 https://github.com/jonapoul/aktualWhat 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.00083 | $0.01118 |
| Opus 5 | $0.00042 | $0.00559 |
| Sonnet 5 | $0.00017 | $0.00224 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
dependency-browser 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Browser
Resolve a Maven dependency from the local Gradle cache and extract it into
build/dependency-browser/<group>/<artifact>/<version>/ so the caller can browse
its contents without leaving the project directory.
Input
Expect coordinates in one of these forms:
group:artifact:version— extract the main JAR (classes + resources)group:artifact:version:sources— extract the sources JAR insteadgroup:artifact— look up the version fromgradle/libs.versions.tomlfirstgroup:artifact:sources— look up the version, then extract the sources JAR
Step 0 — Resolve version if omitted
If the version field is missing or the classifier is sources in the third position,
look it up from gradle/libs.versions.toml before proceeding.
Search the toml for the group+artifact pair in the [libraries] section:
grep -n '<group>\|<artifact>' gradle/libs.versions.toml
The entry will look like:
some-alias = { module = "group:artifact", version = "1.2.3" }
# or with a version ref:
some-alias = { module = "group:artifact", version.ref = "some-version" }
If it uses version.ref, look up the ref in the [versions] section:
grep 'some-version' gradle/libs.versions.toml
Use the resolved version string. If not found in the toml, report clearly and stop.
Extraction target
Always extract into the project's build directory:
build/dependency-browser/<group>/<artifact>/<version>/
or for sources:
build/dependency-browser/<group>/<artifact>/<version>-sources/
Steps
1 — Check if already extracted
ls build/dependency-browser/<group>/<artifact>/<version>[-sources]/ 2>/dev/null
If files are listed, report the extraction dir and stop — do not re-extract.
2 — Locate the JAR in the Gradle cache
The local Gradle cache lives at ~/.gradle/caches/modules-2/files-2.1/. Search it:
# Main JAR
find ~/.gradle/caches/modules-2/files-2.1/<group>/<artifact>/<version> \
-name "<artifact>-<version>.jar" ! -name "*sources*" ! -name "*javadoc*" \
2>/dev/null
# Sources JAR
find ~/.gradle/caches/modules-2/files-2.1/<group>/<artifact>/<version> \
-name "<artifact>-<version>-sources.jar" \
2>/dev/null
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 · 135 lines · 83 tokens per session scan A c46df0becded
dependency-browser is an agent published in the GitHub repository jonapoul/aktual (32 stars, last pushed yesterday), licensed Apache-2.0. It adds 83 tokens to every session and 1,118 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-09-01.
Other agents, from other repositories
kotlin-expert
Expert in Kotlin programming language, focusing on idiomatic Kotlin code, coroutines, extension functions, and memory management.
mobile-developer
Cross-platform mobile development specialist for React Native and Flutter. Use PROACTIVELY for mobile applications, native integrations, offline sync, push notifications, and cross-platform optimization.
Comet Squad
AI team for Comet MVU framework development. Manages the src/Comet subproject.
Marketing Report Builder
Agent "Marketing Report Builder" from muratgur/ordinus, covering role, capabilities, requested work, instructions and marketing report builder.
mobile-architect
Mobile architecture expert. Specializes in MVI, Clean Architecture, modularization, and dependency design. Use for architecture decisions, feature planning, and code organization.
compose-guide
Jetpack Compose patterns specialist. Guides on state management, recomposition optimization, theming, animations, and Compose best practices. Use when building or reviewing Compose UI.