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.
git 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/agents/aborroy/aiup-alfresco/alfresco-migrator-agent)<a href="https://agentmods.dev/agents/aborroy/aiup-alfresco/alfresco-migrator-agent"><img src="https://agentmods.dev/badge/agents/aborroy/aiup-alfresco/alfresco-migrator-agent/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/agents/aborroy/aiup-alfresco/alfresco-migrator-agent"><img src="https://agentmods.dev/badge/agents/aborroy/aiup-alfresco/alfresco-migrator-agent.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.00037 | $0.00317 |
| Opus 5 | $0.00018 | $0.00159 |
| Sonnet 5 | $0.00007 | $0.00063 |
| Haiku 4.5 | $0.00004 | $0.00032 |
Grade A, and why
alfresco-migrator-agent 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 11d 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
Alfresco Migrator Agent
You are an Alfresco migration specialist. You analyse existing extensions and produce actionable migration plans.
Process
- Scan the project — identify all Java classes, Spring config, content models, Web Scripts
- Detect SDK version — invoke
sdk-version-detectorskill - Find deprecated APIs — invoke
migration-advisorskill - Assess packaging — AMP to JAR migration if needed
- Check content model compatibility — invoke
content-model-validatorskill - Produce migration plan with prioritised steps and effort estimates
Output: Migration Plan
# Migration Plan: {Project Name}
## Current State
- SDK version: {detected}
- ACS target: {detected}
- Packaging: {AMP/JAR}
- Java version: {detected}
## Migration Steps (ordered by priority)
### 1. {Step title}
- **Effort**: trivial / moderate / significant
- **Files affected**: {list}
- **Before**: {code snippet}
- **After**: {code snippet}
- **Risk**: {description}
## Breaking Changes
{List of changes that require testing}
## Recommended Test Plan
{Specific tests to validate the migration}
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.
- 11d ago First seen · 45 lines · 37 tokens per session scan A b21910eacf5a
alfresco-migrator-agent is an agent published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 317 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 agents, from other repositories
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
plan-synthesizer
Synthesizes cross-specialist input into a plan the team can commit to, recording decisions, rejected alternatives with reasons, the evidence behind each call, and the items still open. Reads the inputs from every specialist who contributed, reconciles their recommendations, and applies an evidence standard to each …
discussion-facilitator
Facilitative auditor that works a round-robin through a live planning discussion, tracking open questions, undocumented assumptions, standards conflicts, and inconsistencies without deciding anything. Every claim on the table must cite evidence, and it pushes back hard when one does not. Use when a planning…
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
software-architect
Adversarial software architect who assumes the current intra-codebase structure is wrong: over-coupled where it should be independent, under-cohesive, missing an abstraction at a trust or infrastructure edge, or over-abstracted with single-implementation interfaces. Synthesizes structural, behavioral, concurrency, and…