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 agentmods add commands/aborroy/aiup-alfresco/auditgit 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/commands/aborroy/aiup-alfresco/audit)<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/audit"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/audit.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.00037 | $0.02422 |
| Opus 5 | $0.00018 | $0.01211 |
| Sonnet 5 | $0.00007 | $0.00484 |
| Haiku 4.5 | $0.00004 | $0.00242 |
Grade A, and why
audit 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit — Custom Audit Application Generator
In-Process SDK only — audit applications deploy inside the ACS JVM as part of the Platform JAR. They record audit data driven by repository actions and audit-producing services (e.g. the
alfresco-accessdata producer).
Generate a custom audit application, its data extractors/generators, and the properties that enable it, from requirements.
Input
Read REQUIREMENTS.md to identify audit requirements:
-
Resolve the Platform JAR project's
Root pathfrom Section 2 (Project Architecture).- If Section 2 contains no
Platform JARproject, stop and explain that/auditonly applies to the in-process Platform JAR project.
- If Section 2 contains no
-
Read the "Audit requirements" sub-section (Section 7 Behaviour Requirements or a dedicated audit section).
- If no audit requirements are present, stop and ask the user to run
/requirementsfirst (or provide a description as$ARGUMENTS). - Identify which audit data producer drives the application (commonly
alfresco-accessfor node CRUD; or a custom audit call), and which values must be recorded.
- If no audit requirements are present, stop and ask the user to run
-
From Section 2, derive:
{platform-project-root}—.for Platform JAR only mode;{name}-platform/for Mixed mode{module-id}— the Platform JAR artifactId (bare artifact ID, e.g.my-extension). Read from<artifactId>in the platformpom.xmlor derive as{platform-artifactId}from Section 2. Never use the fullmodule.idproperty value as the directory name.{java-package}— the Java package declared in Section 2{prefix}— the namespace prefix declared in Section 5 (Content Model Requirements)
-
Derive from audit requirements:
{App}— PascalCase audit application name (e.g.DocumentAccess){app-key}— the application key, conventionally{prefix}or{prefix}-{app}(lowercase)- The audit paths/values to record (e.g. node ref, user, action, a custom property)
- Whether a custom data extractor is needed (to derive a recorded value from the audit data map) and/or a data generator (to inject a value not present in the source data)
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 · 240 lines · 37 tokens per session scan A ec854d0e9599
audit is a command 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 2,422 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 commands, from other repositories
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
claude-recall
Update project context using the local LLM (Qwen2.5 0.5B).
review
Submit a story for verification (In Progress → In Review, no PR yet).
standup
Alias of /board — the async sprint snapshot.
wp-cleanup
Find and clean up unused PHP code, Composer dependencies, imports, and dead code in WordPress projects.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.