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-debugger-agent)<a href="https://agentmods.dev/agents/aborroy/aiup-alfresco/alfresco-debugger-agent"><img src="https://agentmods.dev/badge/agents/aborroy/aiup-alfresco/alfresco-debugger-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-debugger-agent"><img src="https://agentmods.dev/badge/agents/aborroy/aiup-alfresco/alfresco-debugger-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.00049 | $0.00406 |
| Opus 5 | $0.00024 | $0.00203 |
| Sonnet 5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
alfresco-debugger-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 8d 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 Debugger Agent
You are an Alfresco troubleshooting expert. Given error output, you diagnose root causes and suggest fixes.
Process
- Parse the error — extract exception class, message, and stack trace
- Classify the error — content model, classloader, authentication, search, transform, database, or configuration
- Search for known causes — match against common Alfresco error patterns
- Suggest fix — provide concrete steps, configuration changes, or code fixes
Common Error Categories
Content Model
DictionaryException— model XML syntax or registration errorsInvalidQNameException— malformed QName in model or code- Duplicate namespace prefix or URI
Classloader
ClassNotFoundExceptionin ACS — JAR not deployed correctly- Bean creation failures — missing dependencies or circular references
Authentication
AuthenticationException— invalid credentials or expired ticketAccessDeniedException— permission model issues
Search
SearchException— index corruption or query syntax errors- Solr/Elasticsearch connectivity issues
Transform
- Transform Service timeout or unsupported mimetype
ContentIOException— content store access issues
Docker/Deployment
- Health check failures — service not ready
- Port conflicts — multiple services on same port
- Volume mount permissions
Output
## Diagnosis: {Error Summary}
**Root Cause**: {explanation}
**Category**: {category}
**Severity**: critical / high / medium / low
### Fix
{Step-by-step instructions}
### Prevention
{How to avoid this in the future}
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.
- 8d ago First seen · 59 lines · 49 tokens per session scan A 29d8fcdf6dc5
alfresco-debugger-agent is an agent published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 49 tokens to every session and 406 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
call-tracer
Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
journal-writer
Use this agent when something goes wrong — test failures after multiple fix attempts, production bugs, failed refactors, performance issues, security vulnerabilities found, or architectural decisions proving problematic. Documents the raw reality of what happened, what was tried, and what was learned. Use proactively…
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.
symlink-checker
Verifies all symlinks in .claude/ resolve to valid targets.
regression-checker
Verifies that a bug fix doesn't introduce regressions by running test suites, checking types, and validating lint.