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 rest-api-validatorgit 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/rest-api-validator)<a href="https://agentmods.dev/skills/aborroy/aiup-alfresco/rest-api-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/rest-api-validator.svg" alt="Measured on agentmods" 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.00085 | $0.00785 |
| Opus 5 | $0.00043 | $0.00392 |
| Sonnet 5 | $0.00017 | $0.00157 |
| Haiku 4.5 | $0.00009 | $0.00078 |
Grade A, and why
rest-api-validator 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 6d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REST API Validator
Validate the given Alfresco v1 Public REST API resources against these rules. This is the
modern annotation-based framework (org.alfresco.rest.framework), not classic Web Scripts.
Annotation Validation
- Every entity resource class must be annotated
@EntityResource(name = "...", title = "..."). - Every relationship resource class must be annotated
@RelationshipResource(name = "...", entityResource = X.class, title = "..."), and itsentityResourcemust reference an existing@EntityResource-annotated class in the project. - The
nameon both annotations must be plural, kebab-case (e.g.vendor-contracts,payments) and contain no verbs.
Action Method Validation
- The resource class must implement at least one interface from
org.alfresco.rest.framework.resource.actions.interfaces—EntityResourceAction.Read/ReadById/Create/Update/Delete, orRelationshipResourceAction.Read/Create/Update/Delete. - FLAG as ERROR any public action method (
readAll,readById,create,update,delete) that is missing@WebApiDescription.- Why it breaks: the framework only maps annotated methods. An unannotated action method
is silently unreachable and the operation returns
405 Method Not Allowed. - Fix: add
@WebApiDescription(title = "…")to every action method.
- Why it breaks: the framework only maps annotated methods. An unannotated action method
is silently unreachable and the operation returns
- A
readAllmethod must returnCollectionWithPagingInfo<T>— FLAG as ERROR a rawList<T>/Collection<T>return (bypasses the paging envelope).
Model POJO Validation
- The returned/consumed model POJO must have exactly one getter annotated
@UniqueId.- FLAG as ERROR zero
@UniqueIdgetters (framework cannot buildreadById/ serialise id). - FLAG as ERROR more than one
@UniqueIdgetter (ambiguous identifier).
- FLAG as ERROR zero
- The POJO should be a plain JavaBean: public no-arg constructor, getters/setters, no Alfresco service fields.
Forbidden Patterns
- FLAG as ERROR a resource class that
extends DeclarativeWebScript— that is the classic framework and will not be discovered byResourceLookupDictionary. - FLAG as ERROR
@Autowired— use setter injection wired inwebscript-context.xml. - WARN if
@PostConstructor@Transactionalappears on a resource class.
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.
- 6d ago First seen · 56 lines · 85 tokens per session scan A 5a1b1456879f
rest-api-validator is a skill published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 785 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-08-30.
Other skills, from other repositories
tactical-ddd
Design, refactor, analyze, and review code by applying the principles and patterns of tactical domain-driven design. Triggers on: domain modeling, aggregate design, 'entity', 'value object', 'repository', 'bounded context', 'domain event', 'domain service', code touching domain/ directories, rich domain model…
review-workflow-management
This skill reviews the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) that an app exposes for Dapr Workflows. Use this skill when the user asks to "review workflow management", "audit workflow management API", "check workflow HTTP endpoints", or similar.
review-workflow-activity
This skill reviews Dapr Workflow activity implementations for idempotency, retries, error boundaries, and convention violations. Use this skill when the user asks to "review workflow activities", "check activity idempotency", "audit Dapr activities", or similar.
laravel-architecture-review
Review a Laravel codebase's architecture and design, not just its types. Use when asked to audit a Laravel app, find architectural smells, decide where business logic belongs (controller vs Action vs Service), whether a Repository/DDD/TDD layer is justified, or how to apply SOLID/DRY to a Laravel project. Runs the…
breaking-change-detector
Use this skill to help API producers and consumers find actual or potential breaking changes — REST/OpenAPI, GraphQL, gRPC/Protobuf, or consumer-driven contracts — and apply SemVer and deprecation discipline. Trigger on "will this change break our API consumers", "how do I detect breaking changes in our OpenAPI spec"…
api-design-review
Invoked helper skill for higher-risk API contract decisions, usually called from /research or /write-a-prd. Use when the unresolved question is API shape, compatibility, auth, webhook design, or paradigm choice. Not a default top-level workflow step or a substitute for ordinary implementation work.