AgentScope Java is a framework for building distributed software agents that use language models to perform tasks over extended sessions. It is intended for enterprise applications needing agent coordination, controlled tool use, isolated workspaces, event streaming, and distributed session management. The catalogue entries provide skills and instructions for working with this framework.
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 skills add agentscope-ai/agentscope-java --skill verify-changesgit clone --depth 1 https://github.com/agentscope-ai/agentscope-javaWrote 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/agentscope-ai/agentscope-java/verify-changes)<a href="https://agentmods.dev/skills/agentscope-ai/agentscope-java/verify-changes"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentscope-java/verify-changes/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/agentscope-ai/agentscope-java/verify-changes"><img src="https://agentmods.dev/badge/skills/agentscope-ai/agentscope-java/verify-changes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 14 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 14 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00037 | $0.00379 |
| Opus 5.5 | $0.00015 | $0.00152 |
| Sonnet 5.5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade A, and why
verify-changes 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 1mo 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.
What it actually says
Verify Changes
Editing a file is only half a step. Always close the loop by verifying before you mark work done or open a PR. This is the manual equivalent of an IDE/LSP diagnostics loop.
Procedure
- Detect the project's check commands from its config files:
- Node/TS:
package.jsonscripts (build,lint,typecheck),tsconfig.json->npx tsc --noEmit,npx eslint <changed files>. - Python:
ruff check <path>,mypy <path>,pytest <specific test file>. - Java/Maven:
mvn -q -pl <module> compile, then the single relevant test class via-Dtest=<ClassName>. - Gradle:
./gradlew :<module>:compileJava/:<module>:test --tests <ClassName>.
- Node/TS:
- Run ONLY the checks and tests directly related to the files you changed. Never run the full test suite.
- Disable color output so logs are readable:
NO_COLOR=1,--no-color, or--no-colors. - Read the output as ground truth. If it reports errors, they are real — do not claim success.
- Fix the root cause, then re-run the SAME command. Repeat until it passes.
Rules
- Only mark a todo
completedonce its verification command passes. - If you cannot find a check command, at minimum compile/parse the changed files.
- Do not disable or delete failing tests to make checks pass.
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.
- 1mo ago First seen · 29 lines · 37 tokens per session scan A 321708d56510
verify-changes is a skill published in the GitHub repository agentscope-ai/agentscope-java (6,013 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 379 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
GitHub Issues
Triage GitHub issues, extract the real ask, and connect each issue to the relevant files, tests, or release surface before acting.
Test Driven Development
Drive behavior changes through a failing test, the smallest working implementation, and then cleanup once the behavior is locked.
benchmark-design
Design and calibrate a multi-Case capability Benchmark and establish a traceable Formal Baseline, or import a published Benchmark package.
agent-evaluation
Run one specified Test Agent on one specified Benchmark Case exactly once, privately score that execution, and return one protocol result.
agent-optimization
Improve an Agent State through versioned scores and score-linked Traces from a frozen Benchmark.
Skill: Verify skill
Skill for opinionated verification workflow for validating code changes.