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/bootstrap-loadergit 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/bootstrap-loader)<a href="https://agentmods.dev/commands/aborroy/aiup-alfresco/bootstrap-loader"><img src="https://agentmods.dev/badge/commands/aborroy/aiup-alfresco/bootstrap-loader.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 | $0.00034 | $0.02686 |
| Opus 5 | $0.00017 | $0.01343 |
| Sonnet 5 | $0.00007 | $0.00537 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade A, and why
bootstrap-loader 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 4d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bootstrap-loader — Bootstrap Data Loader Generator
In-Process SDK only — bootstrap loaders deploy inside the ACS JVM as part of the Platform JAR. Never use
@PostConstructorApplicationReadyEventfor repository data initialisation — they fire on every server restart and will create duplicate data.
Generate an Alfresco module component that initialises folders, categories, or reference data exactly once per module version per repository.
Input
Read REQUIREMENTS.md to identify bootstrap loader requirements:
-
Resolve the Platform JAR project's
Root pathfrom Section 2 (Project Architecture).- If Section 2 contains no
Platform JARproject, stop and explain that/bootstrap-loaderonly applies to the in-process Platform JAR project.
- If Section 2 contains no
-
Read Section 7 (Behaviour Requirements) sub-section "Bootstrap loader requirements".
- If no bootstrap loader requirements are present in Section 7, stop and ask the user to run
/requirementsfirst (or provide a description as$ARGUMENTS).
- If no bootstrap loader requirements are present in Section 7, 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){groupId}— the Maven groupId declared in Section 2
-
Derive from bootstrap loader requirements:
{LoaderName}— PascalCase loader name (e.g.ArchiveFolders,CategoryReference){sinceVersion}— the module version from which this loader applies (e.g.1.0)- What data to create: folders (with paths under Company Home), categories, or reference nodes
Output Files
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.
- 4d ago First seen · 264 lines · 34 tokens per session scan A 5c3620b9832e
bootstrap-loader is a command published in the GitHub repository aborroy/aiup-alfresco (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,686 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.