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/alphaaiservice/cortex/gen-docsgit clone --depth 1 https://github.com/alphaaiservice/cortexWhat 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.00060 | $0.15983 |
| Opus 5 | $0.00030 | $0.07991 |
| Sonnet 5 | $0.00012 | $0.03197 |
| Haiku 4.5 | $0.00006 | $0.01598 |
Grade B, and why
gen-docs scanned grade B with 2 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo yum update -y && sudo yum install docker docker-compose-plugin -y Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:[port]/health How it starts
The opening of the file, as written. The whole thing — 2,045 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive Documentation Generator
Generate production-quality documentation for this project based on: $ARGUMENTS
Parse $ARGUMENTS to determine:
- Type:
--type=readme(default if not specified),--type=architecture,--type=api,--type=deployment,--type=local(LOCAL_DEV.md),--type=contributing,--type=manual, or--type=all(generates everything) - Format:
--format=markdown(default) or--format=docusaurus(generates Docusaurus-compatible docs site structure)
--type=local(also part ofall) generatesLOCAL_DEV.mdpercommands/references/LOCAL_DEV_STANDARD.md§4: one-command quickstart, prerequisites + pinned versions, ports table, seed credentials, commonmakecommands, hybrid native-hot-reload mode, themake verifyboot check, and the full Troubleshooting matrix. Whenever the README is generated it MUST carry a top-level "## Run Locally" section (the 3-line quickstart, linking LOCAL_DEV.md).
If no arguments are provided, default to --type=all --format=markdown (generate all documentation in standard Markdown).
Step 1: Analyze Project for Documentation
Before generating any documentation, perform a deep project scan. Run all detection tasks in parallel using the Agent tool.
1A: Discover Project Identity
# Project name and metadata
cat package.json 2>/dev/null | grep -E '"name"|"version"|"description"|"license"|"author"'
cat pyproject.toml 2>/dev/null | head -30
cat setup.py 2>/dev/null | head -30
cat Cargo.toml 2>/dev/null | head -20
cat go.mod 2>/dev/null | head -5
Extract:
- Project name (from package.json name, pyproject.toml project.name, or directory name)
- Version (from package.json version, pyproject.toml version, or git tags)
- Description (from metadata or README first line)
- License (from LICENSE file or metadata)
- Author/Team (from metadata, CODEOWNERS, or git log)
1B: Scan Project Structure
# Map the full directory tree (excluding noise)
find . -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/venv/*" \
-not -path "*/__pycache__/*" -not -path "*/.next/*" -not -path "*/dist/*" \
-not -path "*/.mypy_cache/*" -not -path "*/.ruff_cache/*" -not -path "*/.pytest_cache/*" \
-type f | head -300
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 · 2,045 lines · 60 tokens per session scan B 02af30161be2
gen-docs is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 60 tokens to every session and 15,983 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
alfred
Asistente contextual de Alfred Dev. Enruta automáticamente al flujo o comando operativo correcto.
feature
Ciclo completo de desarrollo: producto, arquitectura, desarrollo, QA, docs, entrega.
_composicion
Protocolo interno compartido para la composición dinámica del equipo de Alfred según tarea, stack y señales runtime.
ajustes
Configura Alfred Dev: autonomía, proyecto, Lucius, memoria y personalidad. Antes /alfred-dev:config.
audit
Auditoría completa del proyecto con 4 agentes en paralelo.
discuss
Refina una idea o feature antes de abrir un flujo completo de implementación.