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/fabioc-aloha/Alex_Skill_MallWrote 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/fabioc-aloha/alex_skill_mall/add-source)<a href="https://agentmods.dev/commands/fabioc-aloha/alex_skill_mall/add-source"><img src="https://agentmods.dev/badge/commands/fabioc-aloha/alex_skill_mall/add-source/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/commands/fabioc-aloha/alex_skill_mall/add-source"><img src="https://agentmods.dev/badge/commands/fabioc-aloha/alex_skill_mall/add-source.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.00025 | $0.00646 |
| Opus 5 | $0.00013 | $0.00323 |
| Sonnet 5 | $0.00005 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
add-source 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 yesterday.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/add-source
Add a new source store (a third-party plugin repo) to the Mall's registry. Runs the store-evaluation scorecard first; on Accept, registers in sources/supported-stores.json and verifies the next scan picks it up.
Steps
- Apply store-evaluation to the proposed remote URL. Score against the five dimensions (maintenance, adoption, license, ACT fit, docs). If total < 7, decline and record rationale in the conversation.
- On Accept (score ≥ 7):
- Determine
name(kebab-case, ≤32 chars, matches the conventional short identifier) - Determine
pluginDir(where plugins live in the upstream repo:.,plugins,skills,agents, etc.) - Determine
qualitytier:internal,official,community-curated,community,domain, orreference - Determine
provenance: false(third-party) and knownlicenseif extractable from upstream
- Determine
- Add the entry to
sources/supported-stores.json(alphabetical byname). - Run
node scripts/scan-sources.cjslocally withSOURCES_DIRpointing at a temp dir; verify the new store producescatalog/stores/<name>.jsonwith a plausible plugin count. - Run
node scripts/compute-trust.cjsandnode scripts/render-catalog.cjs; confirm the new store appears inREADME.mdranked by trust. - Commit
[behaviour] add source: <name> (<one-line rationale>). - Push and let Monday's cron produce the first full catalog refresh against the new source.
Boundaries
- Do not skip the scorecard. Stores below score 7 do not get added even if the requester insists — record the decline.
- Do not invent
qualitytier; if the upstream doesn't fit an existing tier, propose a new tier in a separate ADR-style discussion first. - Do not bypass
provenance: truefor any third-party store. Provenance is for first-party Mall-curated only. - Do not commit catalog regeneration in the same commit as the registry edit; let the cron own that refresh so the diff is reviewable.
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.
- yesterday First seen · 37 lines · 25 tokens per session scan A e8cd443f6059
add-source is a command published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 646 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
issue-prd-generation
You are generating a comprehensive Product Requirements Document (PRD) for a GitHub issue. This PRD will be passed to a separate AI agent instance with ONLY THIS CONTEXT for implementation. Write with that constraint in mind.
artifact-insight-scan
Analyze the provided project artifacts for missed insights, action items, and follow-ups that should become tracked issues.
post-pr-retrospective
You are running as the retrospective agent for a closed pull request.
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.