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/setup-ai-operations)<a href="https://agentmods.dev/commands/fabioc-aloha/alex_skill_mall/setup-ai-operations"><img src="https://agentmods.dev/badge/commands/fabioc-aloha/alex_skill_mall/setup-ai-operations/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/setup-ai-operations"><img src="https://agentmods.dev/badge/commands/fabioc-aloha/alex_skill_mall/setup-ai-operations.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.00027 | $0.00271 |
| Opus 5 | $0.00014 | $0.00135 |
| Sonnet 5 | $0.00005 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
setup-ai-operations 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 9d 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
/alex-act-ai-operations setup-ai-operations
Use setup-ai-operations to configure provider access.
Steps:
- Load the setup skill and determine whether this is onboarding or preparation for an approved execution.
- During onboarding, do not ask for API keys, tokens, or other credentials, and do not initiate provider login. Report key-free planning readiness and stop.
- Defer provider login and authentication until an approved execution plan selects a provider and execution requires access.
- For post-selection preparation, confirm which provider and model the approved plan selected.
- Route hosted providers through native login and local providers through the exact host environment variable or approved secret storage, without requesting or printing the value.
- Route hosted-provider login through its first-party flow.
- Preview the exact ElevenLabs runtime before any package installation.
- Ask separately before applying the preview.
- Verify each selected provider and report partial readiness honestly.
Would revise by 2026-11-11 if setup remains undiscoverable or bypasses the preview and consent boundary.
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.
- 9d ago First seen · 31 lines · 27 tokens per session scan A ec4de916a743
setup-ai-operations is a command published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 271 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-08-31.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.