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 aborroy/aiup-alfresco --skill sdk-version-detectorgit clone --depth 1 https://github.com/aborroy/aiup-alfrescoWrote 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/aborroy/aiup-alfresco/sdk-version-detector)<a href="https://agentmods.dev/skills/aborroy/aiup-alfresco/sdk-version-detector"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/sdk-version-detector/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/aborroy/aiup-alfresco/sdk-version-detector"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/sdk-version-detector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00048 | $0.00570 |
| Opus 5 | $0.00024 | $0.00285 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
sdk-version-detector 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 9d 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
SDK Version Detector
Detect which Alfresco SDK the project uses and report which code generation patterns apply.
Detection Logic
- Search for
pom.xmlin the project root and submodules - Check
<parent><artifactId>:alfresco-sdk-aggregator→ In-Process SDK (Maven)alfresco-java-sdk→ Out-of-Process SDK (Spring Boot)
- If neither parent is found, check for
alfresco-java-event-api-spring-boot-starterdependency → Out-of-Process - If still unclear, check for
alfresco.platform.versionoracs.versionproperties → In-Process
SDK Types
In-Process SDK (Maven SDK alfresco-sdk-aggregator)
Deploys as a Platform JAR or AMP inside the ACS JVM.
| SDK Version | ACS Version | Java | Spring | Patterns |
|---|---|---|---|---|
| 4.x (≤4.11) | 6.x–7.x | 11 | 5.x | Legacy ServiceRegistry, XML-only config |
| 4.x (4.12+) | 25.x–26.1 | 17+ | 6.x/Boot 3.x | Web Scripts, XML for integration points, Java config for internal wiring |
Use for: behaviours, web scripts, actions, content model bootstrap — anything that must run inside the Alfresco JVM.
Out-of-Process SDK (Spring Boot SDK alfresco-java-sdk)
Runs as a separate Spring Boot application outside ACS, connected via ActiveMQ and REST.
| SDK Version | ACS Version | Java | Spring Boot | Patterns |
|---|---|---|---|---|
| 7.x | 25.x–26.1 | 17+ | 3.x | @AlfrescoEventListener, standard Spring Boot @Configuration |
Use for: event listeners, external integrations, async processing — anything that reacts to repository events over ActiveMQ.
Output
Report:
- Extension type: In-Process or Out-of-Process
- Detected SDK and version
- Detected ACS version
- Java version requirement
- For In-Process: whether to use XML or Java-based Spring configuration
- For Out-of-Process: confirm event API and ActiveMQ configuration patterns
- Any version-specific warnings
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.
- 9d ago First seen · 51 lines · 48 tokens per session scan A 064ca3787da3
sdk-version-detector is a skill published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 570 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
spring-boot-engineer
Generates Spring Boot 3.x configurations, creates REST controllers, implements Spring Security 6 authentication flows, sets up Spring Data JPA repositories, and configures reactive WebFlux endpoints. Use when building Spring Boot 3.x applications, microservices, or reactive Java applications; invoke for Spring Data…
java-architect
Use when building, configuring, or debugging enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming. Invoke to implement WebFlux endpoints, optimize JPA queries and database performance, configure Spring Security with OAuth2/JWT, or resolve authentication issues and async processing…
112-java-maven-plugins
Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) …
121-java-object-oriented-design
Use when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object creation, methods, or exception…
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…
111-java-maven-dependencies
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a…