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/feature-mapgit 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.00024 | $0.03382 |
| Opus 5 | $0.00012 | $0.01691 |
| Sonnet 5 | $0.00005 | $0.00676 |
| Haiku 4.5 | $0.00002 | $0.00338 |
Grade A, and why
feature-map 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Map — Codebase Feature Dependency Graph
Map features for: $ARGUMENTS (default: entire project)
Build a complete visual map of all features in the codebase, their dependencies, database tables, API endpoints, and frontend pages. Generates Mermaid diagrams and a text report. Works for ANY stack.
KEY PRINCIPLE: Map what actually exists in the code, not what you assume. Every node in the graph must trace back to real files.
Step 1: Scan for Features
1.1: Detect Project Structure
# Find all route/controller/handler files (API endpoints)
find . -type f \( -name "*route*" -o -name "*controller*" -o -name "*handler*" -o -name "*view*" -o -name "*endpoint*" -o -name "*api*" \) -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/venv/*" -not -path "*/__pycache__/*"
# Find all service/use-case files (business logic)
find . -type f \( -name "*service*" -o -name "*usecase*" -o -name "*use_case*" -o -name "*manager*" -o -name "*provider*" \) -not -path "*/node_modules/*" -not -path "*/.git/*"
# Find all model/entity/schema files (data layer)
find . -type f \( -name "*model*" -o -name "*entity*" -o -name "*schema*" -o -name "*migration*" \) -not -path "*/node_modules/*" -not -path "*/.git/*"
# Find all frontend pages/components
find . -type f \( -name "page.*" -o -name "Page.*" -o -name "*.page.*" \) -not -path "*/node_modules/*" -not -path "*/.git/*"
find . -type d \( -name "pages" -o -name "views" -o -name "screens" \) -not -path "*/node_modules/*" -not -path "*/.git/*"
1.2: Identify Features
Group files into features using directory structure and naming patterns:
Feature Detection Heuristics:
Directory-based: auth/, users/, payments/, products/, search/, etc.
File-prefix-based: auth.service, user.controller, payment.model
Route-based: /api/auth/*, /api/users/*, /api/products/*
Table-based: users, products, orders, payments tables
For each feature, collect:
FEATURE: [Name]
Description: [What this feature does — inferred from code]
Database:
Tables/Collections: [list with key columns]
Migrations: [migration files]
Backend:
Models/Entities: [file paths]
Repositories/DAL: [file paths]
Services: [file paths]
Controllers/Routes: [file paths]
Middleware: [file paths, if any]
DTOs/Schemas: [file paths]
API Endpoints:
[METHOD] [path] — [purpose]
Frontend:
Pages: [file paths]
Components: [file paths]
State/Store: [file paths]
API Client: [file paths]
External Dependencies:
APIs: [third-party APIs used]
SDKs: [external SDKs]
Services: [external services — Stripe, SendGrid, etc.]
Internal Dependencies:
Depends on: [other features this feature imports/calls]
Depended by: [other features that import/call this feature]
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 · 416 lines · 24 tokens per session scan A ae646b42b956
feature-map is a command published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 25d ago), licensed MIT. It adds 24 tokens to every session and 3,382 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
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.