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/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/rest-api-validator"><img src="https://agentmods.dev/badge/skills/aborroy/aiup-alfresco/rest-api-validator.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.00085 | $0.00785 |
| Opus 5.5 | $0.00034 | $0.00314 |
| Sonnet 5.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 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.
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.
- 1mo 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 (14 stars, last pushed 2d ago), licensed Apache-2.0. It adds 85 tokens to every session and 785 once invoked, about $0.0003 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
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…
api-contracts
API design and contract engineering — REST resource modelling, error envelopes, pagination, filtering, idempotency, versioning and deprecation, rate limiting, webhooks, OpenAPI, GraphQL schema and N+1 defence, and contract testing. Use when designing, reviewing or documenting an endpoint or integration; when the user…
performance-engineering
Performance engineering across the stack — Core Web Vitals (LCP, INP, CLS), bundle size and rendering strategy, image and font optimisation, backend latency budgets, caching layers, database query cost, profiling, and load testing. Use when the user says "slow", "performance", "optimize", "Core Web Vitals", "LCP"…
review-pubsub-subscriptions
Reviews Dapr pub/sub subscriptions and handlers in .NET and Python (declarative, programmatic, streaming) for CloudEvent handling, response statuses, idempotency, dead-letter handling and duplicate subscriptions. Use for "review my Dapr subscribers" or "check pub/sub handlers for idempotency".
review-workflow-activity
Read-only audit of existing Dapr Workflow activities for idempotency, retries, error boundaries and conventions, with DWF-ACT-NNN findings. Use for "review workflow activities" or "audit Dapr activities". For guidance while writing an activity use the catalyst-ai plugin.
review-workflow-management
Read-only audit of the HTTP management endpoints (start, status, terminate, pause, resume, raise-event, purge) an app exposes for Dapr Workflows, with DWF-MGT-NNN findings. Use for "review workflow management" or "check workflow HTTP endpoints". To operate runs on Diagrid Catalyst use the catalyst-ai plugin.